• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: gitlab-branch-source-plugin, workflow-multibranch-plugin
• Labels:

  • gitlab
  • multi-branch
  • pipeline
  • status

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

Jussi Mullo created issue - 2022-02-08 13:40

Jussi Mullo made changes - 2022-02-08 13:42

Description

Original: 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 statuses 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?

New: 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?

Jussi Mullo made changes - 2022-02-10 10:39

Component/s

New: workflow-multibranch-plugin [ 21465 ]

Alex Earl made changes - 2022-11-17 13:10

Component/s		New: gitlab-branch-source-plugin [ 21980 ]
Component/s	Original: _unsorted [ 19622 ]