-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
jenkins 2.19.4
github-organization-folder 1.5
The drop down dialog to select github org scan credentials only lists `UsernamePasswordCredentialsImpl` credentials. While the `github` plugin also supports `StringCredentialsImpl` credentials – I found this rather confusing as I only use github API tokens. I have a preference for using API tokens with robots as it is somewhat easier to revoke access.
- is related to
-
JENKINS-33228 GitHub server configuration undocumented / duplicated
-
- Open
-
Currently you use API tokens in org folders by creating them as a `UsernamePasswordCredentialsImpl` with the username that they belong to as the username.
The way that the `github` plugin stores credentials is actually incorrect and there will be some fix-up of that as part of JENKINS-33228 at which point there will be a dedicated `GitHubApiTokenCredentials` implementation that will be easier to use and (hopefully) allow for easier creation (in the ideal form you would click a button and that would redirect to github and return the created token... but remains to be seen if that UX can be provided for)