[JENKINS-55726] GitHub commit status context not unique enough or configurable - jobs always overwrite each other

GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository.

Multiple jobs configured against the same source repo will incorrectly set all checks successful if the last completed check is successful.

In my opinion, if there is no mechanism to define mandatory and optional checks, then the worst status check should provide the overall result.

This could be a check prior to submitting status that validates the prior status is not unsuccessful, and  it is the same git sha1, and it is a different job name.

The secondary issue here is that only a single link is added to the PR, and so there is no indication on the GitHub PR how many jobs ran.

---
Originally reported by j3p0uk, imported from: GitHub commit status context not unique enough or configurable - jobs always overwrite each other

• status: Open
  
• priority: Critical
  
• component(s): github-api-plugin, github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 9
  
• imported: 2025-12-02
  

Raw content of original issue

GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository.


Multiple jobs configured against the same source repo will incorrectly set all checks successful if the last completed check is successful.


In my opinion, if there is no mechanism to define mandatory and optional checks, then the worst status check should provide the overall result.


This could be a check prior to submitting status that validates the prior status is not unsuccessful, and  it is the same git sha1, and it is a different job name.


The secondary issue here is that only a single link is added to the PR, and so there is no indication on the GitHub PR how many jobs ran.

environment

```
CloudBees Jenkins Enterprise 2.107.34.0.1-fixed

GitHub API Plugin 1.90

GitHub Branch Source Plugin 2.3.5
```