Can't access fork pipeline status from upstream
Summary
When our server was updated from 11.5.x-ee to 11.11.3-ee the system stopped showing pipeline status for merge requests. I originally thought it was the same issue a #27111 (closed) and commented on it at the time but after I made a new comment I was asked by a member of the GitLab team to raise a new issue with my issue.
We use a forking workflow and prior to the upgrade colleagues could see the pipeline status of each others merge requests and the pipeline status was one of the elements used to make a judgement on MR approval. Developers could see if the overall pipeline status was pass or fail.
After the server updated to 11.11.3-ee and and with no other changes made, developers could no longer see the pipeline status of each others merge requests. On the merge request page the message would be Could not retrieve the pipeline status. For troubleshooting steps, read the documentation
. The gitlab server has been updated a number of times since (currently on 12.1.6-ee) and the issue still persists. Below is a screenshot of how MR's look now:
Steps to reproduce
- Developer 1 forks the main repo
company/tool
toandy/tool
- Developer 1 creates a new branch
US123
onandy/tool
- Developer 1 creates a new MR from
US123
onandy/tool
tomaster
oncompany/tool
- Developer 2 reviews the new merge request on
company/tool
Prior to upgrading to 11.11.3-ee Developer 2 would see that the pipeline had passed or failed
What is the current bug behaviour?
- Developer 2 sees the pipeline status is shown as
Could not retrieve the pipeline status. For troubleshooting steps, read the documentation
- Developer 2 cannot see the pipeline tab on the MR page, with all the previous
What is the expected correct behaviour?
This was the behaviour prior to upgrading to 11.11.3-ee
- Developer 2 sees the pipeline status shown as (for example)
Pipeline #40079 passed for 399f9797 on andy:US123
- Developer 2 can see the pipeline tab on the MR page, with all the previous pipelines run for this MR and their statuses
Other information
We did discover that if a developer enables guest access on their personal fork, which is the source repo/branch of the MR, then pipeline status is viewable again. However this is not a solution as we don't want to and shouldn't have to enable guest access on all the personal forks just to see the overall pipeline status of a merge request. That doesn't seem like the correct behaviour/solution