Auto-Cancel Redundant Pipelines cancels nonredundant pipelines when one job triggers multiple child jobs via the API
Summary
We are on 15.6, self hosted. In a multi-project pipeline, I have job A triggering job B on some-branch via curl, and then job C on some-different branch via curl. Though the child jobs are on different branches, job C is automatically cancelled and never runs, even if I set a sleep period in the job script and confirm job B has finished and is reporting success.
Steps to reproduce
- Set up a multi-project situation, with an "orchestrator" project and a "orchestrated" project.
- In the "orchestrator" project, set up a CI job, with a script that triggers two different jobs in two different branches of the "orchestrated project" via the API.
- Observe that the first job triggered is allowed to run, and the second is cancelled.
Example Project
What is the current bug behavior?
The latter child pipeline is automatically cancelled.
What is the expected correct behavior?
Both pipelines are allowed to run without intervention, as they are on different branches and therefor do not meet the definition of redundancy provided in the settings screen.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)