The path to the repository is on the file system. If CLONE is true, the repository will be cloned here.

Version control system of the repository. Possible values:

• GITHUB
• GITLAB
• OTHER

URL to clone or fetch the repository. It may differ from REPO_FOLLOW_URL if only ssh is used for cloning and commits are web-viewable via HTTP.

Example:

export REPO_FOLLOW_URL=https://github.com/apache/pdfbox

The URL that will be used to generate quick access links to commits on the web server (GitHub or GitLab).

Template for generating quick links for REPO_FOLLOW_URL. The values are set depending on the repository type:

• GITHUB
  %s/commit/%s
• GITLAB
  %s/-/commit/%s

Authentication type to use for clone and fetch. Possible values:

• SERVER_USER_SSH_KEYS
  Use SSH keys for the user for which the CodeHistory service is running.
• USER_AND_PASSWORD
  use REPO_AUTH_USER and REPO_AUTH_PASSWORD
• TOKEN
  use REPO_AUTH_TOKEN.
• TOKEN_AND_USER
  use REPO_AUTH_TOKEN, REPO_AUTH_USER and REPO_AUTH_PASSWORD.
• NO_AUTH
  public repository (does not require authentication)

User login to use for authentication to clone or fetch the repository.

Password to use for authentication to clone or fetch the repository.
Will be encrypted in the cache after initialization from config.json or environment variables.

Token to use for authentication to clone or fetch the repository.
Will be encrypted in the cache after initialization from config.json or environment variables.

Issue tracking system type. Possible values:

• JIRA
• REDMINE
• OTHER

URL of the issue tracking system.

Example:

export ISSUE_TRACKER_URL=https://issues.apache.org/jira

Issue tracking system authentication type. Possible values:

• USER_AND_PASSWORD
• TOKEN
• TOKEN_AND_USER_AND_PASSWORD
• NO_AUTH

Sensitive data will be encrypted in the cache after initialization from config.json or environment variables.

Issue tracking system access key token.
Will be encrypted in the cache after initialization from config.json or environment variables.

Issue tracking system username.

Issue tracking system password.

The RegExp that will be used to extract the issue keys from the commit description.
Default value: ((?<!([A-Za-z]{1,10})-?)[A-Z]+-\d+)
It corresponds to the keys accepted in JIRA, such as ISSUE-12345.

If using Redmine and the ISSUE-id plugin, this should be set to true.

true to fetch the repository periodically, false otherwise.

true to clone the repository into the REPO_PATH, false otherwise.

How many threads to use for indexing.

Branch that will be treated as default.

true to disable index issues data, false otherwise.

Determines if authentication is required to browse the repository.