Pipeline with no job triggered by a new user in the project

We’ve had a new user join our team. When he raises a merge request or “Run pipeline”, a pipeline with no job gets triggered.

  • What are you seeing, and how does that differ from what you expect to see?

In the following screenshot, the 1st, 2nd and 4th pipelines were triggered by this new user, while I triggered the 3rd pipeline (which I later cancelled).

When I go into the first pipeline (or the 2nd/4th), I see that it has no jobs.

  • What version are you on? Are you using self-managed or GitLab.com?
    I’m using Gitlab.com

  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)
    This is the .gitlab-ci.yml file:

image: node:latest

stages:
  - prebuild
  - build

variables:
  LC_ALL: "en_US.UTF-8"
  LANG: "en_US.UTF-8"
  GIT_STRATEGY: clone

# Cache modules in between jobs
cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - node_modules/
    - .npm/

before_script:
  - npm install -g appcenter-cli

default-job:
    script: echo "default job"
    stage: prebuild

build-job:
  stage: build
  script:
    - bash gitlabCLscript.sh
  only:
    - merge_requests
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
    • I thought it might have been because of permissions issue, so tried to promote the new member. Added him to the private group to which this project belongs too.
    • Earlier my gitlab-ci file wasn’t passing CI validation tool, so I added the default-job above (now the validation passes, but the same problem remains).

Let me know if any more information is needed.

I’m experiencing the exact same issue. Any update from support?

Folks, any updates on this? We’ve been paying for pipeline minutes and due to this issue and lack of response (not only on this topic but looking at others as well), considering moving away from gitlab’s CI/CD.