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
My connections, click on Source control and services, and scroll down to the
Custom git repositoriessection.
ADD NEW CUSTOM GIT REPOSITORY....
- Enter your username and password, and specify the URL for the repository.
- (Optional) Click
Test connectionto confirm that the 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.
- 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
443for HTTPS (or port
- 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 name
salesforce-metadatawill be in a repository called
- Your server needs a public DNS. If https://dnschecker.org cannot resolve your server name, then Gearset cannot connect to it.
Contact our team and we'll be happy to help. See how.