Triggers stuck as pending, downstream jobs never created

Since a couple of days now all our pipelines show as pending. The triggers show as pending and no jobs are created.
I initially thought this was due to the unavailability of shared runners but after leaving it for over 24 hours the status still had not changed.
Cancelling and starting the pipeline again the pipeline did not help either.
I have noticed however this seems to only affect merge request pipelines. Running the pipeline on a branch works fine

image


Using Gitlab.com
Using shared runners

The same gitlab-ci.yml is used for merge request and branch pipelines.
Meaning if one works, the config is valid.
It was all working fine and started misbehaving yesterday (5th July 2022)

As stated above I have tested the pipeline on a branch and it works fine. Only merge request pipelines are not started or rather stuck in pending state

1 Like

We are having the same problem. I figured out that the configuration is broken due to some change in GitLab.
Here is what I have done temporarily for some pipelines to check if they work.
In the child pipeline, we have workflow rules.
I have changed this to rules for each job and it seems to start working. Can you confirm if your issue is related?

# childpipeline.yml
child-job1:
   stage: test
   script: echo test1

child-job2:
   stage: test
   script: echo test2

workflow:
   rules:
      - changes
        - sub-proj/**
        - sub-proj/**/**

to

# childpipeline.yml
child-job1:
   stage: test
   script: echo test1
   rules:
      - changes
        - sub-proj/**
        - sub-proj/**/**

child-job2:
   stage: test
   script: echo test2
   rules:
      - changes
        - sub-proj/**
        - sub-proj/**/**

We don’t use workflow in our gitlab-ci.yml. Instead we have rules for each job. So what you changed to is already what we were doing…

@urielle oh ok. Maybe it is something similar. Because we were also facing the same issue past 2 days, and after this change everything is normal.

1 Like

My bad, our child pipeline was using workflow rules. I have tested on one of them the change you suggested and indeed the job gets created.
Thanks @vinod.blaze !

Curious as to what has changed there on GitLab side? Looked at the documentation but haven’t spotted anything

Yeah no idea. Gitlab does not even respond to premium support tickets.

@vinod.blaze looks like the issue has been resolved… merge request pipelines are now running as expected (without any changes).

Yes. We reverted our changes already.