We have a ci job that triggers a child pipeline in the same project. It was running fine up until a recent upgrade from 16.1.1 to 16.2.4 and now it hangs on that job and must be canceled manually. Note also that in the UI, I can no longer expand the job to look at the jobs in the child pipeline. I think it boils down to this:
gitlab-ci.yml:
stages:
- trigger
trigger-job:
stage: trigger
trigger:
include: child-gitlab-ci.yml
strategy: depend
child-gitlab-ci.yml:
stages:
- triggered
test-job:
stage: triggered
script:
- echo "Running unit tests... This will take about 5 seconds."
- sleep 5
- echo "Unit test job is complete"
Has something changed in how we should trigger child pipelines?
The parent job also uses a resource_group to manage a concurrency problem but that doesn’t seem to come into play here so I didn’t include it in the sample. I also tried adding a rule in the client pipeline job that also didn’t change the behavior.
rules:
- if: $CI_PIPELINE_SOURCE == “parent_pipeline”
The job is stuck in the running state:
And here is what it looked like prior to the gitlab upgrade:
Thanks for any advice,
Jim