Jenkins GitHub Repository Item Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
===Credentials=== | ===Credentials=== | ||
Credentials used to scan branches and pull requests, check out sources and mark commit statuses. For GitHub, only "username with password" credentials are supported, credentials of other kinds will be filtered out. This is because Jenkins uses GitHub API, which does not support other ways of authentication. If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub. If your organization contains private repositories, then you need to specify a credential from a user that has access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo". | |||
===Owner=== | ===Owner=== | ||
===Repository=== | ===Repository=== | ||
Revision as of 23:58, 31 December 2019
External
Internal
General
Display Name
Different from the item name.
Branch Sources
GitHub
Credentials
Credentials used to scan branches and pull requests, check out sources and mark commit statuses. For GitHub, only "username with password" credentials are supported, credentials of other kinds will be filtered out. This is because Jenkins uses GitHub API, which does not support other ways of authentication. If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub. If your organization contains private repositories, then you need to specify a credential from a user that has access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo".