To run a comparison in Gearset, you need to add a source and target location of your metadata. Gearset supports comparing and deploying metadata that is source controlled, with support for any git-based source control provider.
You can add connections via OAuth to the following providers:
Azure DevOps Git
You can also connect to any git-based source control system using a username/password. This includes Google Cloud Source Repositories, which can also be authenticated in this way. Note that, if you’re using Google Cloud Source Repositories, you need at least one branch in your repository before Gearset can authenticate it.
Adding a source control connection via OAuth
My Connectionson the left-hand side menu, click on Source control and services
+ Connect tonext to the required source control provider
Log in to your account
When prompted, grant Gearset access to the repository
When connecting to GitLab, for example, click
Authorize to grant Gearset access, then follow the default OAuth authentication flow.
Adding a source control connection via username/password
Custom git connections can be added with the instructions below, but note that, in this way, only one single repository is available (as opposed to all the repositories, using the OAuth method).
My connectionson the left-hand side menu, click on Source control and services
Scroll down to the
Custom git repositoriessection, and click on
ADD NEW CUSTOM GIT REPOSITORY...
Enter your username and password, and specify the URL for the repository
Test connectionto confirm that Gearset can access your repository
Add repositoryto save the connection
Your connection will now be listed on the Source control and services page.
If your account uses 2FA, you may need to create a custom application password for Gearset to connect to your repository.
If you are using the
SSHAuthentication type and a non-default port (22) is used, you may need to format the repo address with a
This git repository will now appear under
Source control >
Custom Git when you compare metadata.
Note: If you are using a GitLab repository as a target of a deployment, you will need to add it as a custom git connection first. This is due to a GitLab limitation that does not allow applications to use OAuth tokens as credentials in a git push.
Viewing and deleting saved source control connections
All of the source control connections you have added to Gearset can be seen in the
My connections section, on the Source control and services page.
To remove a saved connection, click the bin icon under the
Changing the source control authentication username
If you'd like to update a saved connection to a new username (e.g. update your GitHub user that is linked to Gearset), you'll need to remove the connection and clear your cache before adding the new username.
You can clear you cache by either:
Logging out of your source control account via their web UI (e.g. log out of GitHub.com); or
Opening a new incognito or private tab of your browser to add the new connection; or
Revoking the OAuth token in the original source control connection
If you don't clear the cached connection, Gearset may re-use the previously saved connection from your browser.