You can manage and view your CI jobs on CI dashboard page.

This includes viewing the history of your CI deployments, editing CI job settings, configuring webhooks for your CI jobs, as well as previewing any open or pending PRs for a specific job.

To see the deployments executed by a specific CI job you, need to click on View history button next to the CI job (highlighted in black on below screenshot).

For successful CI job runs, you'll be able to download the PDF deployment report, package deployed, and the CSV summary, just like any other deployment in the app.

Additionally, you can also find the roll back option if you want to revert the changes made by your CI job.

For any failed CI job deployments, clicking the View errors button will show you the full list of deployment errors - these are usually validation errors, many of which we have documented here.

These errors can be exported as a CSV file for easy reference and debugging.

If there are any pending PR validations targeting your CI job, Gearset will display the list of such PR validations nested under your CI job.
​
If a CI job belongs to your Gearset Pipeline and there are PRs, you can also preview these PRs on our dedicated Deployment pipelines page.
​
Note that each PR (pull request) validation job has its own View history button.
​
By clicking on the job, and selecting the View history button next to a given PR, you can preview the history of a specific PR validation.

Once you View history of a specific PR, you can:

You are able to filter the CI job history in a number of ways.

Firstly, with a few options depending on whether the run is successful or not.
​
You can filter CI job history based on:
- All job runs
- Only the runs with attempted changes (such as job runs where new, changed, or deleted items got deployed)
- Successful runs (completed deployments)
- Failed runs (uncompleted deployments; nothing got deployed)
- Partially successful runs (e.g. when your CI deployment job combines metadata + CPQ, but only metadata got deployed successfully)
- Only runs with errors (e.g. validation errors)

Secondly, you are able to filter by date - by default, the CI job history will display job runs created in the last 10 days.

You can change this filter view by clicking on the date range drop-down menu.

As well as running static code analysis, Gearset will apply problem analyzers to all CI jobs.

If problem analyzers have applied fixes to your CI job, you'll be able to click the View problem analysis fixes button to view those fixes in detail.

You can read more on how problem analyzers work in a CI job.

As well as running during manual deployments and in change monitoring jobs, Gearset’s fully configurable static code analysis also automatically runs as part of your CI jobs.

Gearset will automatically perform your static code analysis (on the classes being deployed) every time a CI job runs.

To find your static code analysis results, click View static code analysis issues for any of the CI job runs to see the code analysis issues for that run.

Gearset will display any detected rule violations and group them within the class that they belong to.

You can click the menu on the left to view specific violation categories or use the text filter (top right) to narrow your results down to a specific class.

For any violation detected, Gearset will tell you which line of code the issue begins on and provide a description of the violation, so you can easily understand why issues have been flagged.

For more detailed information on each specific rule, click the name of the rule, and you’ll be taken to the PMD library for a more in-depth look at the individual rule and its implementation.

On your CI dashboard, in the Edit settings of every CI job navigate to Deployment gates section.
​
This allows you to control whether to fail the CI job if the static code analysis rules are detected.

You have two options to choose from:

A Gearset user who is not the owner of a CI job can still preview CI job settings in our app.

However, certain level of permission is required for this option to become available.

Previewing CI setting is only possible if a user has Deployment level access for the target org of the CI job.

The CI job owner can assign such access in Orgs Permissions page in our app (more guidance on assigning permission in this article).

Users with Deployment level access to the target org of a CI job will be able to click on View settings button to preview all the configuration for a given job.

On the Pipelines & CI jobs page, a Gearset user with a Member status would need the following access to be able to view CI job settings: