Run pipelines

After creating and configuring pipelines in ALM Octane, run the pipelines on your CI server. You can even trigger such a run from ALM Octane.

What happens when a pipeline runs?

When a pipeline runs, the following occurs:

  • A graphical representation is displayed of your CI server pipeline steps and their results.

  • ALM Octane collects the results of the automated tests that run as part of the pipeline. ALM Octane creates automated test entities associated with the test run results it collects. If a relevant automated test already exists, the results are associated with that test.

    View the automated tests alongside the manual tests in ALM Octane. View the test run results when tracking the quality of your products and releases.

    Note: If you delete a pipeline after running it, this does not remove any automated tests or test run results from ALM Octane.

  • ALM Octane collects any available SCM commit information.

Back to top

Run the pipeline from ALM Octane (Optional)

DevOps admin permissions are required.

  1. In the ALM Octane Pipelines module, open the Pipelines tab and select a pipeline.

  2. Click Run Pipeline.

    ALM Octane triggers the CI server to run the pipeline's root job.

    On Jenkins and Bamboo, the pipeline steps run under the CI Server user that you specified when configuring the HPE ALM Octane CI plugin. The pipeline run is limited by the permissions assigned to this user.

    As the steps in the pipeline run, colors change to show the status of the step.

    Color Description
    Gray

    Has not yet run.

    A gray step may also indicate a step that no longer runs as part of the pipeline. The more times the pipeline runs without running this step, the less vividly the step appears in the pipeline.

    White Running or ran.

As each step in the pipeline finishes, either a or a indicates the status of the step run.

Back to top

View pipeline run results

After your pipeline runs, you can see the status of each step, summarized information about the last completed run, the history of previous runs, overall statistics for the pipeline, and more.

In ALM Octane, go to the Pipelines module, click Pipelines and select a pipeline from the list of pipelines on the left. Use the following options to track and analyze the quality of your build:

  • Check the pipeline status (in the list of pipelines on the left) When the pipeline finishes, ALM Octane provides information about the pipeline run results. The pipeline results are aggregated (combined) at the highest level, the pipeline root.

    Example:  

    A pipeline fails on the CI server. This pipeline runs automated tests. Of these tests, 230 passed and 5 failed.

  • Learn about your last pipeline run and the overall quality of your builds (Overview tab)

    The top half of the overview tab displays data from the last completed run.

    The bottom half shows you a larger picture of the pipeline quality, based on data collected from multiple pipeline runs.

    The Build success rate is based on all pipeline runs, since the pipeline was created. The other widgets are based on the most recent runs.

  • See the status of each pipeline step (Topology tab)

    As each step in the pipeline finishes, its graphical display provides information about the results. For details on this view, see Explore the pipeline.

    Example:  

    • A pipeline step completes successfully on the CI server.

    • A pipeline step fails on the CI server. This step runs automated tests. Of these tests, 20 passed and 5 failed.

  • Drill down into the pipeline to more information:

    • Click the pipeline's ID to open the pipeline.

      In the Details tab, view information about the pipeline as a whole, based on data collected from multiple pipeline runs. This enables you to quickly review the overall build success rate, trends of test results and run durations, as well as a break down of pipeline runs by status.

      In the Runs tab, you can see all pipeline runs, dating back to when you added the pipeline to ALM Octane.

      Click the ID of a specific run to view more details and to analyze test failures. In a run's Details tab, you can add tags to label the run. The tags are displayed in the pipeline's list of runs, and can be used to group pipeline runs in dashboard widgets.

    • Click the number to the right of the pipeline name to view details about the last or current run.

  • Follow links in the pipeline steps (Topology tab)

    • Click a step's name to open the job on the CI server.

    • Click the build number to open the specific run on the CI server.

    • Click the test statuses to open the tests in the Quality module.

Back to top

Analyze test failures

If a pipeline run includes failed automated tests, use the Failure Analysis tab to learn more about the failing tests.

Based on your analysis, you might decide to edit your automated test, create a defect for an area in your application, or even extend you project's timeline or reduce the planned content.

Open a specific pipeline run:

  • To open the last or current run, click the number to the right of the pipeline name.

  • To open a previous run, click the pipeline's ID to open the pipeline. In the Runs tab, click the ID of a specific run.

For details, see Analyze automated test failures.

Back to top

Track code changes

If your Jenkins or Bamboo server is set up to work with an SCM system, open a pipeline run to see commit changes and stories associated with that run.  For details, see Track changes committed to your Source Control Management system.

Back to top

View and share a summary of your pipelines

In the Pipelines module, click Summary to see a summary of your pipeline runs. If you have multiple pipelines running, you can click Choose Pipelines to view a subset of them, or to search for a specific one.

The summary provides information about the pipeline's history, its status, and progress. You can see: 

  • The status of the last few runs.

  • What triggered the last run (system or commit).

  • If triggered by a commit, you can see who committed and what files changed.

  • The progress of the current run.

  • After the tests are completed, an aggregated summary of the test run results.

This view is suitable, for example, for displaying on a group plasma screen. This enables the whole group to view the overall build status and quality.

Back to top

Next steps: