I agree with you on this sentiment. When I took over this plugin it has always been a part of it that has been sorely lacking. I plan to revamp the permissions and set them up so that a user can choose what permissions anybody gets in Jenkins based on their access in GitHub (think similar to the matrix-based authorization strategy).
For now, as a workaround. I highly recommend making use of the matrix-based authorization strategies. I personally use the Job DSL plugin and the project matrix-based authorization strategy in a large Jenkins installation (~600+ users with ~1300+ jobs). For now, that works for me. However, I agree that part of the GitHub authentication plugin needs some love.
I'll use this issue to track enhancing this feature.
See also https://wiki.jenkins-ci.org/display/JENKINS/GitHub+OAuth+Plugin#GitHubOAuthPlugin-MatrixbasedAuthorizationstrategy
I agree with you on this sentiment. When I took over this plugin it has always been a part of it that has been sorely lacking. I plan to revamp the permissions and set them up so that a user can choose what permissions anybody gets in Jenkins based on their access in GitHub (think similar to the matrix-based authorization strategy).
For now, as a workaround. I highly recommend making use of the matrix-based authorization strategies. I personally use the Job DSL plugin and the project matrix-based authorization strategy in a large Jenkins installation (~600+ users with ~1300+ jobs). For now, that works for me. However, I agree that part of the GitHub authentication plugin needs some love.
I'll use this issue to track enhancing this feature.
See also https://wiki.jenkins-ci.org/display/JENKINS/GitHub+OAuth+Plugin#GitHubOAuthPlugin-MatrixbasedAuthorizationstrategy