[JENKINS-52382] Can't stop / cancel private repository builds

Hello there,

 

Using the "GitHub Committer Authorization Strategy" with the following settings:

When a member of the organization is launching a build of a private repository of this organization he can't abort of build which is problematic for us because they have to ask an administrator which lead to waste of time.

It's ok for public repositories but permissions on private ones seems broken for the cancel permission.

Note that the users don't have the stop button on BlueOcean nor on the "classic" interface.

Sorry if that's already reported, I saw a lot of issue related to cancel permission but none of them were matching this use case with github oauth authorization.

Also I can't really use a project matrix based authorization strategy given the number of repository / teams under the organization (not an option)

---
Originally reported by clementgautier, imported from: Can't stop / cancel private repository builds

• assignee: sag47
  
• status: Open
  
• priority: Major
  
• component(s): github-branch-source-plugin, github-oauth-plugin, github-plugin
  
• resolution: Unresolved
  
• votes: 4
  
• watchers: 6
  
• imported: 2025-12-02
  

Hello there,


 

Using the "GitHub Committer Authorization Strategy" with the following settings:




When a member of the organization is launching a build of a private repository of this organization he can't abort of build which is problematic for us because they have to ask an administrator which lead to waste of time.


It's ok for public repositories but permissions on private ones seems broken for the cancel permission.


Note that the users don't have the stop button on BlueOcean nor on the "classic" interface.


Sorry if that's already reported, I saw a lot of issue related to cancel permission but none of them were matching this use case with github oauth authorization.


Also I can't really use a project matrix based authorization strategy given the number of repository / teams under the organization (not an option)

• environment: Jenkins 2.129 (but the issue is pretty old)

- [Screenshot from 2018-07-05 10-41-44.png](https://issues.jenkins.io/secure/attachment/43326/Screenshot%20from%202018-07-05%2010-41-44.png)
>