-
Improvement
-
Resolution: Fixed
-
Major
-
None
We are trying to use same app on Jobs across orgs and is not working as we need to maintain duplicate credentials for multiple organization.
Maintaining same credentials for multiple orgs seems duplicate to me, is there any chance we can avoid this?
Our use case is, since it is internal (GitHub Enterprise) bot, it is pretty open and we don't even know who would invite this bot to their organization, and this bot does takes care of creating Jenkins job through DSL scripts, which is using the standard credentials. So it is very hard to keep creating credentials on the fly for every org that this bot is being invited to.
Thanks a bunch for all the help on maintaining this awesome plugin. Let me know your thoughts please.
Related discussion on PR: https://github.com/jenkinsci/github-branch-source-plugin/pull/290#discussion_r415168275
- causes
-
JENKINS-65006 Couldn't authenticate with GitHub app ID when app is installed in 2+ organizations
- Open
-
JENKINS-65007 Resource not accessible by integration error authenticating with GitHub app with the wrong owner
- Open
- is blocked by
-
JENKINS-68480 github app credential does not work for pipeline-github-plugin
- Resolved
- is duplicated by
-
JENKINS-62594 Scanning private repos of GitHub user accounts with GitHub App credentials fails
- Closed
- is related to
-
JENKINS-64662 Create GitHub App Credentials Binding to support owner override
- In Review
-
JENKINS-64870 Enhance GitHupAppCredentials to use JWTToken instead AppInstallation Token
- Closed
- relates to
-
JENKINS-57351 Support for making Jenkins a "GitHub App"
- Resolved
-
JENKINS-70984 Unable to clone repository when pr author has no push or admin permission
- Open
- links to