To run a comparison in Gearset, you need to add a source and target location of your metadata. Gearset supports comparing and deploying metadata, CPQ configuration, and Vlocity Data packs that are source-controlled with any Git-based provider. You can connect to your source control provider via two methods. First, we support the following providers via OAuth:
Additionally, Gearset integrates with custom Git repositories via a username and password. We describe both methods in our support doc on managing source control connections in Gearset.
Common issues
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. This is described in Github's guide on Managing your PATs.
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 static IP addresses.
To ensure a secure connection, Gearset will only connect using
HTTPSand 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
.git. For example, in Bitbucket a project with the namesalesforce-metadatawill be in a repository calledhttps://bitbucket.gearset.com/kevin_boyle/salesforce-metadata.git.Your server needs a public DNS. If https://dnschecker.org 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
127.16.0.0 to 127.31.255.255
192.168.0.0 to 192.168.255.255
Need help?
See our guide on how to contact Gearset support.