Pipeline run failure analysis insights

A pipeline's Failure Analysis Insight cards show you the most critical problems in your pipeline run. This helps you focus on fixing the most important issues first.

Overview

ALM Octane analyzes information regarding failed tests, problematic tests, build failure classification, related committers, and more. This data is then presented in the pipeline overview to give CI owners actionable information to fix failed pipelines quickly.

To access Failure Analysis Insights, in the Pipelines > Pipelines tab, select a pipeline on the left. The cards appear above the Pipeline Run Overview section. Click the right and left arrows to navigate between the cards.

ALM Octane categorizes pipeline failures into three types: Compilation, Environment, or Quality issues. The cards for each of these are displayed in order of urgency. Each card shows you the problem and its root cause, the users directly related to the problem, and the percentage of issues being handled. This information tells you if a problem needs immediate attention and whom to contact in order to deal with it.

Note: To provide data for Failure Analysis Insights, you need to manually classify failed builds. For details, see Build failure classification.

Back to top

Compilation Issues

Compilation issues include any failure with at least one build which failed due to compilation issues. Related users includes anyone who may have caused the issue (generally committers in the pipeline run), as well as anyone assigned in the compilation build's Who's on it field.

For each build that was classified as a compilation issue, the card shows if it failed in an earlier run, so you know when the failure started. The bottom of the card indicates the percentage of builds that have someone assigned in the Who's on it? field, indicating that the problem is being handled.

You can click on the number of builds, or on a specific build name, to drill to the relevant Failure Analysis details.

Back to top

Environment Issues

Environment Issues include any build failures classified as Environment issues. The cards are divided into subgroups based on the out-of-the-box tags (such as Environment - Database, and Environment - Network), or custom tags you added. Each card shows all the problematic jobs in the relevant category, with the oldest jobs listed first.

Related users includes anyone assigned in the relevant builds' Who's on it? field. The bottom of the card indicates the percentage of builds that have someone assigned in the Who's on it? field.

You can click on the number of builds, or on a specific build name, to drill to the relevant Failure Analysis details.

Back to top

Quality Issues

If any tests failed in a pipeline run, and the build is not classified as a compilation or environment issue, you will see a Quality Issue card. The cards are divided into two types: Quality - Builds with most failed tests, and Quality - Committers related to most test failures.

Tip: Admins can define a percentage threshold that determines which test failures are displayed on the card. For details, see the FAILURE_ANALYSIS_INSIGHT_TEST_FAILURE_THRESHOLD configuration parameter under FAILURE_ANALYSIS_INSIGHT_TEST_FAILURE_THRESHOLD.

You want to focus your attention on test failures that are stable and indicate a regression that needs to be fixed quickly. The Quality - Builds with most failed tests card therefore shows you the number of test failures that are stable, out of the total test failures. These are either tests that are failing consistently or failed for the first time in this run.

Related users include any committers who may have caused the issue or anyone assigned in the test runs' Who's on it? field. The bottom of the card indicates the percentage of tests in these builds that have someone assigned in the Who's on it field.

You can click on the number of builds, or on a specific build name, to drill to the relevant Failure Analysis details showing stable test failures.

The Quality - Committers related to most test failures card shows you which committers are related to the most test failures. Committers are listed in order of the number of stable test failures that they impacted, so you know whom to contact to resolve problems.

The bottom of the card indicates the percentage of tests that are being handled, regardless of who is handling them.

You can click on a line showing a number of tests to drill to the relevant Failure Analysis details showing test failures related to the selected committer.

Back to top

See also: