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. If you use one of the popular hosted services such as GitHub or BitBucket then you can connect to those using OAuth.
If you need to connect to a git server that you're running on-premise then you can still do that using Gearset's support for manual connections.
Adding a source control connection via username/password
- Under Manage connections, on the Connections page, click on the Source control and Jira tab and scroll down to the Manage custom git repositories section
- Click Add new git repository
- Enter your username and password, and specify the URL for the repository
- (Optional) Click test connection to confirm that the Gearset can access your repository
- Click Add repository to save the connection
Your connection will now be listed on the connections page.
Common Issues
- If your account uses 2FA, you may need to create a custom application password for Gearset to connect to your repository.
- Gearset will need to be able to connect to your git server so it needs to accept connections from the following IP addresses on port
443:52.30.99.114,34.246.69.148,34.246.80.170, and52.208.77.76 - 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
Having issues?
Contact our team and we'll be happy to help. See how