Go to Gearset
All Collections
Troubleshooting
Version control
Connecting to popular on-premise source control systems
Connecting to popular on-premise source control systems
This article walks through how to connect to popular on-premise source control systems via username/password, and how to troubleshoot issues
Valerio Chang avatar
Written by Valerio Chang. Updated over a week ago

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 connect to them either by OAuth or using Gearset's support for manual connections - adding a custom git repository via a username and password. We describe both methods in our support doc on managing source control connections in Gearset. This article will focus on the manual method.

Adding a source control connection via username/password

  1. Under My connections, click on Source control and services, and scroll down to the Custom git repositories section.

  2. Click ADD NEW CUSTOM GIT REPOSITORY....

  3. Enter your username and password, and specify the URL for the repository.

  4. (Optional) Click Test connection to confirm that the Gearset can access your repository.

  5. Click Add repository to save the connection.

Your connection will now be listed on the Source control and services page.

Common issues

  1. If your account uses 2FA, you may need to create a custom application password (also known as personal access token) for Gearset to connect to your repository.

  2. For GitHub with HTTPS as the authentication type you will need to enter a personal access token in place of a password, as described here.

  3. If HTTPS method doesn't work due to your git server settings, please try the SSH method.

  4. Gearset will need to be able to connect to your git server, so it needs to accept connections from our static IP addresses.

  5. To ensure a secure connection, Gearset will only connect using https and your server needs to be set up with a valid certificate from a CA. Self-signed certificates are not supported as they can't guarantee a secure connection.

  6. You need to use the correct path to your git repository. This typically is a path that ends in .git . For example, in Bitbucket a project with the name salesforce-metadata  will be in a repository called https://bitbucket.gearset.com/kevin_boyle/salesforce-metadata.git.

  7. Your server needs a public DNS. If https://dnschecker.org cannot resolve your server name, then Gearset cannot connect to it.

Need help?

Contact our team and we'll be happy to help. See how.

Did this answer your question?