[JENKINS-67758] MR pipeline status in GitLab is not valid if one commit triggers multiple individual multibranch pipelines

We have a monorepo with multiple multibranch pipeline jobs that are triggered on their own if the commit changes their part of the repo.

If an MR happens to trigger multiple jobs, it seems that all those jobs related to the same commit will change the pipeline status of the MR, meaning that the last job that finishes also sets the final status, no matter if the other ones have failed or succeeded.

Is there maybe a way to make these individual jobs to be shown as stages in the MR pipeline? Or is the only way around this to have a single upstream pipeline that wraps all these individual pipelines?

---
Originally reported by jmullo, imported from: MR pipeline status in GitLab is not valid if one commit triggers multiple individual multibranch pipelines

• status: Open
  
• priority: Major
  
• component(s): gitlab-branch-source-plugin, workflow-multibranch-plugin
  
• label(s): gitlab, multi-branch, pipeline, status
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

We have a monorepo with multiple multibranch pipeline jobs that are triggered on their own if the commit changes their part of the repo.


If an MR happens to trigger multiple jobs, it seems that all those jobs related to the same commit will change the pipeline status of the MR, meaning that the last job that finishes also sets the final status, no matter if the other ones have failed or succeeded.


Is there maybe a way to make these individual jobs to be shown as stages in the MR pipeline? Or is the only way around this to have a single upstream pipeline that wraps all these individual pipelines?

The issue identifies gitlab-branch-source-plugin and workflow-multibranch-plugin, but names no files, tests, or entry points. Start by reproducing a merge request that triggers multiple multibranch jobs and trace how each job updates the commit status; done requires a defined, verified result for combined success and failure status, including whether stages or an upstream pipeline are required.

Written by the indexing model from the issue text.