Gearset

To run a comparison in Gearset, you need to add a source and target location of your metadata. Gearset supports <b>comparing and deploying</b> metadata, <a href="https://docs.gearset.com/en/articles/8420474-comparing-and-deploying-cpq-configuration-with-source-control">CPQ configuration</a> and <a href="https://docs.gearset.com/en/articles/5821967-deploying-salesforce-metadata-and-vlocity-data-packs-together">Vlocity Data packs</a> that is source controlled, with support for any git-based source control provider. You can connect to them either by OAuth 

<a href="https://docs.gearset.com/en/articles/6265095-integrating-with-azure-devops-server">Azure DevOps Server</a>

<a href="https://docs.gearset.com/en/articles/1782885-integrating-with-bitbucket-server">Bitbucket Server</a>

<a href="https://docs.gearset.com/en/articles/4163524-integrating-with-github-enterprise">GitHub Enterprise</a>

<a href="https://docs.gearset.com/en/articles/3885343-integrating-with-self-managed-gitlab">GitLab (self-managed)</a>

- <a href="https://docs.gearset.com/en/articles/6265095-integrating-with-azure-devops-server">Azure DevOps Server</a>
- <a href="https://docs.gearset.com/en/articles/1782885-integrating-with-bitbucket-server">Bitbucket Server</a>
- <a href="https://docs.gearset.com/en/articles/4163524-integrating-with-github-enterprise">GitHub Enterprise</a>
- <a href="https://docs.gearset.com/en/articles/3885343-integrating-with-self-managed-gitlab">GitLab (self-managed)</a>

Or by adding a custom git repository via a username and password. We describe both methods in our support doc on <a href="https://docs.gearset.com/en/articles/618850-managing-source-control-connections-in-gearset">managing source control connections in Gearset</a>. 

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.

For GitHub with HTTPS as the authentication type you will need to enter a personal access token in place of a password, as described <a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token" rel="nofollow noopener noreferrer" target="_blank">here</a>.

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

Gearset will need to be able to connect to your git server, so it needs to accept connections from our <a href="https://docs.gearset.com/en/articles/2678677-gearset-s-static-ip-addresses">static IP addresses</a>.

To ensure a secure connection, Gearset will only connect using <code>HTTPS</code> 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.

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

Your server needs a public DNS. If <a href="https://dnschecker.org/" rel="nofollow noopener noreferrer" target="_blank">https://dnschecker.org</a> cannot resolve your server name, then Gearset cannot connect to it.

Note: Please check that the IP address is not within the following ranges, which are private and will not be accessible outside your network.

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 <a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token" rel="nofollow noopener noreferrer" target="_blank">here</a>.
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 <a href="https://docs.gearset.com/en/articles/2678677-gearset-s-static-ip-addresses">static IP addresses</a>.
5. To ensure a secure connection, Gearset will only connect using <code>HTTPS</code> 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 <code>.git</code> . For example, in Bitbucket a project with the name <code>salesforce-metadata</code>  will be in a repository called <code>https://bitbucket.gearset.com/kevin_boyle/salesforce-metadata.git</code>.
7. Your server needs a public DNS. If <a href="https://dnschecker.org/" rel="nofollow noopener noreferrer" target="_blank">https://dnschecker.org</a> cannot resolve your server name, then Gearset cannot connect to it.
   Note: Please check that the IP address is not within the following ranges, which are private and will not be accessible outside your network.
        - 10.0.0.0 to 10.255.255.255
        - 172.16.0.0 to 127.31.255.255
        - 192.168.0.0 to 192.168.255.255

Contact our team and we'll be happy to help. <a href="https://docs.gearset.com/en/articles/2288721-contacting-gearset-support">See how.</a>

This article walks through how to connect to popular on-premise source control systems via username/password, and how to troubleshoot issues

Common issues

Need help?