Configure SCM (Source control management) connection

As of XL Release 8.2.0, you can store template versions of templates inside a folder in a Source Control Management (SCM) tool. This provides easier management of all the artifacts, the possibility to store them together with Releasefiles and Jenkinsfiles, to configure and to use them from a release pipeline. You can define an SCM connection on a folder level or on a global level in XL Release.

Folder level configuration

To configure automatic synchronization in XL Release on a folder level:

  1. In the top bar, click Design.
  2. Click Folders.
  3. Select a folder.
  4. Click Configurations.
  5. Under Properties, click the plus icon next to Source Control Management. The following options are available:
    • GitHub - template changes will be pushed to the configured GitHub repository.
    • BitBucket Cloud - template changes will be pushed to the configured BitBucket Cloud repository.
    • GitLab - template changes will be pushed to the configured GitLab repository.
  6. Click Save.

Automatic synchronization

The selected template changes will be pushed to the configured repository when the new version of the template is created on the Version control page.

Global level configuration

To configure an SCM connection on a global level that is available throughout XL Release:

  1. In the top bar, click Settings.
  2. Click Shared configuration.
  3. Under Properties, click the plus icon next to Source Control Management. The following options are available:
    • GitHub - template changes will be pushed to the configured GitHub repository.
    • BitBucket Cloud - template changes will be pushed to the configured BitBucket Cloud repository.
    • GitLab - template changes will be pushed to the configured GitLab repository.
  4. Click Save.

For more information about configuration settings shared between folders and tasks, see Create custom configuration types.

GitHub connection options

To setup a GitHub connection:

  1. In the Title field, enter a symbolic name for the SCM configuration.
  2. In the Repository full name field, enter the qualified name of the GitHub repository (<organization_name>/<project_name>).
  3. In the Branch field, enter the name of the branch to which changes will be pushed. The default value is master.
  4. In the Credentials section, select one of the following:
    • Personal access token - Create your own personal access token in GitHub settings.
    • Username and password - Provide username and password to access GitHub.
  5. Click Save.

BitBucket connection options

To setup a BitBucket connection:

  1. In the Title field, enter a symbolic name for the SCM configuration.
  2. In the Repository full name field, enter the qualified name of the BitBucket repository (<organization_name>/<project_name>).
  3. In the Branch field, enter the name of the branch to which changes will be pushed. The default value is master.
  4. In the Credentials section, select one of the following:
    • API key - Provide the BitBucket team name and API key.
    • Username and password - Provide the login username and password to access BitBucket.
    • App password - Provide the username and app password for BitBucket.
  5. Click Save.

GitLab connection options

To setup a GitLab connection:

  1. In the Title field, enter a symbolic name for the SCM configuration.
  2. In the Repository full name field, enter the qualified name of the GitLab repository (<organization_name>/<project_name>).
  3. In the Branch field, enter the name of the branch to which changes will be pushed. The default value is master.
  4. In the Credentials section, select :
  5. Click Save.