[JENKINS-65822] Support multiple github checks against the same PR

Currently, even if I have multiple folders or configurations of the branch source plugin configured, they all report as a single check against the PR.

i.e. If I have repo x, that has an open PR id 123, and I have 2 configurations of branch source plugin each pointing to a different pipeline groovy file. The PR check status in Github will have the status of the project/build that finishes the last.

It will be great if each of the branch source configurations can be differentiated using a name and their statuses can be reported as separate checks against the same GitHub PR.

 

Usecase:

For each open PR, I would like to run some tests against multiple platforms. Currently, I can do this by using different nodes in the pipeline. e.g. a part of the pipeline runs on a Linux node and the other on a windows node. The drawback of this current approach is, if one part of the pipeline fails, I need to run the whole pipeline again.

 

Proposal:

The proposal is to enable having multiple branch source configurations, and each of them report as a seprate check against the same PR. Hence, I could have multiple checks that run and report against the same open PR like - windows, linux and mac, etc. If one part of the pipeline fails, I can re-run that one alone instead of having to replay the whole pipeline. This will also enable breaking down my checks into smaller logical groups, rather than having them all in once single monolithic check.

 

Note:

• Please let me know if there is a way to do this already using the branch source plugin or using some other plugin


• If this sounds like a good feature to be a part of the branch source plugin, I will be happy to spend sometime trying to build, if someone can guide me with some directions

 

---
Originally reported by soorajshajahan, imported from: Support multiple github checks against the same PR

• status: Open
  
• priority: Major
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 3
  
• imported: 2025-12-02
  

Raw content of original issue

Currently, even if I have multiple folders or configurations of the branch source plugin configured, they all report as a single check against the PR.


i.e. If I have repo x, that has an open PR id 123, and I have 2 configurations of branch source plugin each pointing to a different pipeline groovy file. The PR check status in Github will have the status of the project/build that finishes the last.


It will be great if each of the branch source configurations can be differentiated using a name and their statuses can be reported as separate checks against the same GitHub PR.


 


Usecase:


For each open PR, I would like to run some tests against multiple platforms. Currently, I can do this by using different nodes in the pipeline. e.g. a part of the pipeline runs on a Linux node and the other on a windows node. The drawback of this current approach is, if one part of the pipeline fails, I need to run the whole pipeline again.


 


Proposal:


The proposal is to enable having multiple branch source configurations, and each of them report as a seprate check against the same PR. Hence, I could have multiple checks that run and report against the same open PR like - windows, linux and mac, etc. If one part of the pipeline fails, I can re-run that one alone instead of having to replay the whole pipeline. This will also enable breaking down my checks into smaller logical groups, rather than having them all in once single monolithic check.


 


Note:



	
Please let me know if there is a way to do this already using the branch source plugin or using some other plugin

	
If this sounds like a good feature to be a part of the branch source plugin, I will be happy to spend sometime trying to build, if someone can guide me with some directions



 

1 attachment

- [image-2022-02-24-14-05-26-287.png](https://issues.jenkins.io/secure/attachment/57350/image-2022-02-24-14-05-26-287.png)
> 

Start by reading the GitHub check/status reporting path in the branch source plugin and how separate branch source configurations are identified. Verify whether existing plugin configuration can distinguish checks before designing the change. Done means multiple configurations report independently named checks for the same pull request, with each check rerunnable on its own.

Written by the indexing model from the issue text.