Isolate multiple merge request pipeline results
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
I'm using GitLab integrated with Jenkins that performs my CI via gitlab-plugin.
Say I want to merge my feature branch (source) into two target branches (e.g. Develop, Release) at the same time. I raise two merge requests (that point to the same commit on the feature branch). Both MRs trigger pipelines in Jenkins that execute my CI activities. As a result I have two pipelines queued in Jenkins (1.feature->develop, 2. feature->release).
Now, let's assume that I raised the feature->release MR first which gave priority to the corresponding pipeline in Jenkins. The result of this pipeline will update both MRs (raised for feature->develop and feature->release merges) while I would expect only the MR raised for the feature->release merge to get updated. The problem is that commit IDs are targeted by pipelines (both MRs point to the same ones) instead of the MR ids. I would expect isolation here. Is it possible to implement this? Right now I'm testing GitLab and the lack of this feature prevents me from moving to this product (I do have it in TFS).
Thanks.
Intended users
All users
Further details
Such a feature is available in other products.
Proposal
Implement isolation in the GitLab Jenkins plugin by updating a particular MR instead of updating all MRs that come from the same source branch and have the same commit id.
Permissions and Security
N/A
Documentation
N/A
Testing
What does success look like, and how can we measure that?
Enhance code review logic.
What is the type of buyer?
More and more pressure is put on the code quality. Robust features for code review can attract new users.