Creating a merge request immediately after pushing to a source branch results in two pipelines being created
My team use GitLab 14.2.3-ee and we have a problem with the pipeline for branches and merge requests.
When I finish the feature in the feature-branch I push the last commit and immediately create a merge request (MR) to develop-branch.
Push to the feature-branch creates a pipeline for a branch. Creating an MR creates a pipeline for the MR.
Created MR has:
- The pipeline for feature-branch (has several jobs and one of them (deploy) is a manual job)
- The pipeline for MR (has only a build job)
But pipelines run in parallel. Merge request linked with both, but the button “Merge” blocks by pipeline for feature-branch, because it has a manual job.
A message under the button:
Merge blocked: pipeline must succeed. It’s waiting for a manual action to continue.
Looks like the state of the “Merge” button depends on the last succeeded pipeline. In our case, MR-pipeline was created later but succeeded earlier than branch-pipeline.
So, branch-pipeline blocks the button “Merge”.
Can I create sequential pipelines or somehow link MR to MR-pipeline only?