What's the impact on the CI job?
When you run a manual Compare and deploy, after the items to deploy are selected and before the deployment package is created, the problem analyzers kick in.
Problem analyzers are Gearset's intelligent suggestions for your deployment package - their intention is to suggest you to add or remove any components that will help to make your deployment (and its validation) more likely to succeed. You can choose to tick or untick any of these suggestions in order to modify your package.
However, if this kicks in during a CI job deployment, you might not notice this until deployment has completed.
How do the Problem analyzers work in a CI job?
In a CI job scenario, since it is an automated process, all problem analyzers' suggestions are automatically ticked (which may add or remove components to the final deployment package).
The CI job will then proceed with the deployment with problem analyser suggestions applied.
If you would like to verify that problem analyzers are the reason that your item is not being deployed via the CI job, you can view the problem analysis results for the CI job run, as described below.
Alternatively, you can run a manual comparison (via Compare and deploy) with the same source and target environments (as set up in your CI job), using the same metadata filter, and clicking through to see the problem analyzers being triggered.
View problem analysis fixes in CI job history
To see what the problem analyzers are doing under the hood with your CI job, on your CI dashboard navigate to View history for the job in question.
There, you will see a history of your CI job runs with the option to View problem analysis fixes.
Note: The button to preview problem analysis fixes will be greyed out when there are no problem analysis fixes to be shown. This is an expected behavior.
On below example we're seeing that one of the problem analyzers adds a required master-detail field for an object (WebStoreInventorySource) identified in a deployment package. This is so that the deployment doesn't fail when the field isn't added to the package.
This view shows you which problem analyzers made changes to your job, and which items were affected.
How to amend or disable Problem analyzers used in the CI job
In the Ci job settings there is an option for you to change the problem analyzer used by the CI job. You can also choose to not apply any problem analysis fixes.
To amend this option, on your CI dashboard page select Edit settings... for a CI job in question, then navigate to Advanced tab where you have Assigned analysis template setting.
This allows you to apply one of the two default Problem analysis templates:
- Apply all fixes or
- Don't apply any fixes (this entirely disables Problem Analyzers on your CI job).
And if you have any custom templates created tailored to your own needs (where only a set of specific problem analysis fixes may be enabled), you'd also see the Custom templates section:
You can navigate to the Problem analyzer templates page in our app to create your own custom template if you believe it could help your CI job's validation to succeed.