Merge Request Pipeline Status in MRs imported via Direct Transfer loading infinitely
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
When importing Projects with open MRs that have passed their pipeline, neither the pipeline nor the fact that the pipeline passed is imported. This means that when opening the MR on the web, the pipeline status check runs forever and merge is not possible until the "Pipelines must succeed" option is disabled.
Steps to reproduce
- Spin up your own Gitlab instance
- Create a project
- Open an MR
- Run a Pipeline for said MR
- Wait for it to finish successfully
- Got to Gitlab.com
- Import said Project via Direct Transfer
- Make sure "Pipelines must succeed" option is set in project settings
- Go to the MR in the imported project
- Pipeline status check will keep loading instead of displaying status
What is the current bug behavior?
Pipeline status is loading indefinitely.
What is the expected correct behavior?
Either an error message á la "Pipeline not found" or "Pipeline succeeded".
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)