[JENKINS-49800] Use Pipeline name on Pull Request status for GitHub to ease multiple Pipeline in a single repository

I have a single Github Repository, with 2 Jenkinsfiles in 2 different sub-folder of this repository.

On Jenkins, I have 2 Multibranch Pipeline Jobs, both using the GitHub repository (as a GitHub SCM source). They do not use the same Jenkinsfile (pipeline "a" uses "a/Jenknisfile " and pipeline "b" uses "b/Jenkinsfile").

When I create a Pull Request, both Pipeline are triggered, which is expected and normal.

However, the PR status is set on the by both Pipelines: the slower to complete will be the last to set the status.

I understand this use case is not optimal, but as improvement, it could be useful to have the status referencing the pipeline name.

---
Originally reported by dduportal, imported from: Use Pipeline name on Pull Request status for GitHub to ease multiple Pipeline in a single repository

• status: Open
  
• priority: Minor
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-02
  

Raw content of original issue

I have a single Github Repository, with 2 Jenkinsfiles in 2 different sub-folder of this repository.


On Jenkins, I have 2 Multibranch Pipeline Jobs, both using the GitHub repository (as a GitHub SCM source). They do not use the same Jenkinsfile (pipeline "a" uses "a/Jenknisfile " and pipeline "b" uses "b/Jenkinsfile").


When I create a Pull Request, both Pipeline are triggered, which is expected and normal.


However, the PR status is set on the by both Pipelines: the slower to complete will be the last to set the status.


I understand this use case is not optimal, but as improvement, it could be useful to have the status referencing the pipeline name.

• environment: CloudBees Jenkins 2.89.3-4-rolling (Core Jenkins 2.89.3)