Jenkins GitHub Repository Item Configuration

External

• https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin

Internal

• Jenkins Concepts

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".

Owner

GitHub user account or GitHub organization.

Repository

The GitHub repository to scan.

Behaviors

Discover branches

Strategies to discover branches:

• "All branches"
• "Exclude branches that are also filed as PRs"
• "Only branches that are also filed as PRs"

Discover pull request from origin

Strategies:

• "The current pull request revision"

Discover pull request from forks

Strategies:

• Merging the pull request with the current target branch version

Trust:

• Nobody