Source Code Manager Settings

Updated 2 months ago by Michael Cretzman

Currently, this feature is in Beta and behind a Feature Flag. Contact Harness Support to enable the feature. Feature Flags can only be removed for Harness Professional and Essentials editions. Once the feature is released to a general audience, it is available for Trial and Community Editions.

This topic describes the settings in My Source Code Manager. It's a reference you can use when you are trying to find the requirements and options for a specific My Source Code Manager setting.

For instructions on setting up and using My Source Code Manager, see Add Source Code Managers.

My Source Code Manager is required for Harness Git Experience. For details on Harness Git Experience, see Harness Git Experience Overview.

In this topic:

Source Code Manager Overview

In Harness Git Experience, a Harness Project is synced with a Git provider and has multiple Harness Users making commits to multiple branches.

It can be difficult to audit all the Users making commits in the same Project without some way of identifying the users in Harness and your Git provider. Without some way of identifying them, all commits will look like they came from the same person.

A Source Code Manager (SCM) uses your personal Git account information to identify the commits you make. A Source Code Manager is useful for auditing who is making changes to a Project, Pipeline, Connector, etc.

A Source Code Manager is mandatory for Harness Git Experience. If you don’t have a SCM when you try to enable Harness Git Experience, Harness will warn you and require you set one up.

GitHub Authentication

  • Supported Methods: username and Personal Access Token (PAT).
  • Scopes: select all the repo and user options.
  • See also: Creating a personal access token from GitHub.

Bitbucket Authentication

  • Supported Methods:
    • Username and Password.
    • SSH Key. This is the private key. The corresponding public key is added to your Bitbucket account settings.
  • See also: Set up an SSH key from Bitbucket.

GitLab Authentication

  • Supported Methods:
    • Username and Password.
    • Username and Personal Access Token (PAT).
    • Kerberos.
    • SSH Key. This is the private key. The corresponding public key is added to your GitLab account settings.
  • Scopes: select api.
  • See also: Set up your organization from GitLab.

AWS Code Commit Authentication

Azure DevOps Authentication

  • Supported Methods:
    • Username and password.
    • Username and Personal Access Token (PAT).
    • SSH key.
  • Scopes: for Personal Access Tokens, Code: Full.
  • See also: View permissions for yourself or others from Azure.


Please Provide Feedback