As well as managing and viewing your CI jobs, you are also able to view the history of any CI job that has happened in the past. Within this page, you have a number of options to choose from depending on what you are looking to do.

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 rollback option for deployed CI jobs here.

For CI jobs when the deployment failed, clicking the View errors button will show you the full list of deployment errors. These can be exported as a CSV file for easy reference and debugging.

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.

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 affect your CI jobs here.

As well as running during manual deployments and in change monitoring jobs, Gearset’s fully configurable static code analysis now 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 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 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.

Note: You also have the configuration option to fail the CI job if the static code analysis rules are violated.