-
Bug
-
Resolution: Invalid
-
Highest
Let say there are branches X, A, B and C.
The pull-request tests are enabled for all branches and branch specific test is enabled for branch X.
Upon creating PRs to merge X into A, B and C, on each of the 3 PRs, pipeline status shows total 4 pipelines running, 1 for the source branch and 3 for all the 3 PRs.
This is unexpected.
Continuing the above scene,
Let say, there is a conflict in the diff of XtoC PR. Hence this PR pipeline will fail as soon as it starts running.
Now, since other 2 PRs (to branches A and B) are also considering the pipeline status of XtoC PR, they will also show the pipeline status to be failed! Even though those PRs' own pipelines are passing!! When the conflict which caused the fail is not at all related to any of the other PRs' diffs, it should not affect other PRs.
In my case, the above described behavior is blocking the merge of all other PRs.
PS: I did revert the conflicted PR as soon as I spotted the conflict in the diff. But this did not help in any way.
Extra info: I did create all the PRs very quickly one after one.
- relates to
-
BCLOUD-5814 Repository refs for pull requests
- Reviewing