How to confirm what is being deployed by Gearset into your org
If you want to be certain of what is being deployed into your org by a CI job, you can confirm this by checking the deployment comparison & package for any validated PR.
To do this, follow the below steps.
Navigate to the CI jobs page.
Find CI job for the org environment you are deploying into, and expand its dropdown.
In this example, we're looking at "Pipelines Int".
Find the validation for the PR you want to investigate and click on the Validation runs.
In this example, we're looking for a failing run "Breaking-change" on "PR #255"
You will now see a list of all the validation runs for this PR.
Note: If you do not see any run in the list, check the date range selected in the top right.
Click View comparison on the latest run to see what's being included in the deployment using Gearset's comparison view.
Once this has loaded the comparison, you will be able to see all the changes that are being included in the deployment.Note: If there are problem analyzers shown (pointer 2), these will trigger after the comparison and may make additional changes to the final XML package that will be deployed.
If you would prefer to check the deployment package directly, you can find it by downloading the package from the drop down menu on the job run.
This will download the deployment .zip file that is sent to Salesforce. You can use this to check the files directly in a code viewer like Visual Studio Code.
This will give you certainty about what is being pushed into the org with the deployment.
Are some of your changes are missing from the deployment comparison or package?
If there are items that are missing from your deployment package, you can follow the below docs to confirm why they are being missed (all the docs are short and to the point, we promise).
If you could not find the answer above, reach out to support in the In-app chat!
Are there unexpected changes in the deployment comparison or package?
This is likely related to changes being pulled in from your Main branch into your feature branch when you first create it.
We have a document that explains the behaviour here.
To resolve this issue, you will need to open a Sync PR from main to pull in any missed changes. Instructions on how to do this are here.
If you are still facing issues after running a Sync PR or have any questions, feel free to reach out in the In-app chat.