MRs referencing wrong builds in Jenkins
Summary
User reported: We are seeing issues where if we have the same source branch in multiple MRs to different target branch, the latest completed build is being referenced by all MRs associated with that source branch. Jenkins jobs are properly labeled.
Steps to reproduce
Open the multiple MRs with the same source branch.
Example Project
What is the current bug behavior?
All MRs from the same source branch reference the exact same MR build in Jenkins.
What is the expected correct behavior?
MRs from the same source branch should reference the correct MR build in Jenkins.
Relevant logs and/or screenshots
Correct Jenkins build being referenced:
Incorrect Jenkins build being referenced:
Output of checks
This bug happens on GitLab.com
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)
Possible fixes
Workaround
The workaround may be to not open multiple MRs for the same source branch.