Gitlab pipeline not generating

Replace this template with your information

Describe your question in as much detail as possible:

  • What are you seeing, and how does that differ from what you expect to see?
    My gitlab.yml settings are perfect and it was working fine. But today i pushed change on master and my pipeline is not generating.

I tried to create merge request but even i can’t able to merge it as i seen “Checking if merge request can be merged…” this and showing loader all the time.

  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or GitLab.com?
    I am using gitlab.com only.

    • GitLab (Hint: /help): 14.1.0-pre
    • Runner (Hint: /admin/runners): I am using shared runners
  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

before_script:
  - apt-get update -qq
  - apt-get install -qq git

deploy_staging:
  stage: deploy
  environment:
    name: staging
    url: 121.121.121.121
  script:
    - 'which ssh-agent || ( apt-get install -qq openssh-client )'
    - eval $(ssh-agent -s)
    - ssh-add <(echo "$SSH_PRIVATE_KEY")
    - mkdir -p ~/.ssh
    - '[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config'
    - ssh root@121.121.121.121 "cd /home/xyz/public_html/ && git checkout master && git pull origin master && exit"
  only:
    - master

deploy_prod:
  stage: deploy
  environment:
    name: production
    url: 121.121.121
  script:
    - 'which ssh-agent || ( apt-get install -qq openssh-client )'
    - eval $(ssh-agent -s)
    - ssh-add <(echo "$SSH_PRIVATE_KEY_PROD")
    - mkdir -p ~/.ssh
    - '[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config'
    - ssh root@121.121.121 "cd /home/abc/public_html/ && git checkout master && git pull origin master && exit"
  when: manual
  only:
    - master
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
    I search the error on gitlab and can’t get any help from google or docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

Hello.

I am facing the same issue on gitlab.com.

My rules result in CI skipped for certain branches and they can’t be merged when successful pipeline are required as described in the documentation limitation.

Is there a way to mark a pipeline as skipped using rules instead of using skip-ci in commit subject? Because skipped pipeline can be merged when configured.