DevOps main flow

This flow describes how to collect information from your CI server and use it in ALM Octane to measure your release and product quality and to follow your build progress.

Select an image to learn more.

Overview

ALM Octane integrates with your CI/CD processes, enabling you to:

Set up integration with a CI server

DevOps admin permissions are required.

To integrate ALM Octane with your CI server, install and configure the HPE ALM Octane CI plugin.

The steps necessary to setup this integration are described briefly below. For details, see Install and configure the HPE ALM Octane CI plugin on your CI server.

Prerequisites

  • Ask your shared space admin for an API access Client ID and Client secret that the plugin can use to access ALM Octane. For details, see Set up API access for integration.

  • Check that your CI server meets the necessary requirements. For details, see Supported CI and SCM systems.

  • If you are working with Jenkins or Bamboo, decide which CI server user ALM Octane will use to execute jobs on the CI server.

Download, install, and configure the plugin

  1. In ALM Octane, in Settings , click Workspaces and select a workspace.

  2. Click the DevOps tab. On the left side of the pane, select CI Servers.

  3. Download the plugin from the provided link and install it on your CI server.
  4. On the CI server, configure the plugin to connect to ALM Octane.

Back to top

Create a pipeline and explore it

Once connected to a CI server, you can create a pipeline in ALM Octane. Specify the root job for the pipeline, and ALM Octane builds a graphical representation of the job flow starting from that root job.

For Jenkins and Bamboo pipelines, the pipeline also displays the hierarchy of the job flow.

Prerequisites: Define a CI server

DevOps admin permissions are required.

  1. In ALM Octane, in Settings , click Workspaces and select the workspace where you want to define a CI server.

  2. Click the DevOps tab. On the left side of the pane, select CI Servers.

  3. Click + to add a CI server.

  4. Name the CI server.

  5. Select a URL from the list of available servers. The list displays all servers that are set up with the HPE ALM Octane CI plugin to access your ALM Octane.

Create a pipeline:

DevOps admin permissions are required.

  1. In the ALM Octane Pipelines module, select the Pipelines tab and click + to add a pipeline.

  2. Enter a name for the pipeline and, optionally, assign it to a release.

  3. Select a CI server from the list. The list displays all servers created on the CI servers settings page of the current workspace.

  4. Select the root job from which you want ALM Octane to start the pipeline. The list displays the jobs defined on the CI server you selected. If communication with the server fails, the list is not available.

Explore the pipeline

After a pipeline is created, you can graphically see the job steps, their status, and their flow, starting from the root job of the pipeline. For details, see Explore the pipeline.

Note: If you are working with Jenkins: You can similarly create pipelines using the HPE ALM Octane CI plugin on the Jenkins CI server. For details, see Create and configure pipelines in the Jenkins UI.

Back to top

Configure the pipeline (Topology tab)

DevOps admin permissions are required.

After creating a pipeline, you can label and tag it:

  • Labels indicate the job type of a pipeline step. This helps you understand the pipeline flow. In the flat pipeline view, you can also filter the pipeline to show only steps with specific labels.

  • Tags provide testing details and environment information about automated tests that run as part of your pipeline.

Configure tags on pipeline steps that run tests. When the tests run as part of the pipeline, the tests and results are tagged accordingly. You can filter the test run results according to these tags when you analyze the quality of your build, release, or product in ALM Octane.

If a step runs tests that you do not want to track in ALM Octane, simply configure the step to Ignore test run results.

Label a pipeline step:

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

  2. In the Topology tab, click the label at the top right of a step, and select a job type for the step.

    Job types include: Compile, Package, Deploy, and Test.

Configure a pipeline step:

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

  2. In the Topology tab, click Configuration on the bottom right of the step. Add information such as testing framework, test type, testing tool, operating system, browser, and so on. For details, see Configure steps: Define test and test run information.

Note: If you are working with Jenkins: You can similarly configure pipelines using the HPE ALM Octane CI plugin on the Jenkins CI server. For details, see Create and configure pipelines in the Jenkins UI.

Back to top

Run pipelines from ALM Octane

DevOps admin permissions are required.

After you create and configure a pipeline, you can trigger a pipeline run on the CI server from ALM Octane.

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

  2. Click Run pipeline.

    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.

You can see your CI server steps and their results, in a graphical way. For details, see Run pipelines.

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.

Back to top

Assign tests to application modules and backlog items

Assigning automated tests to application modules and backlog items in ALM Octane enables you to view the test results in context. You can then use these results to analyze the progress and quality of your release and product.

You can assign tests to application modules and backlog items manually. You can also set up rules that automatically assign automated tests to specific application modules.

For details on defining application modules or creating your product backlog, see Work with application modules and Build the product backlog.

Manually assign a test to application modules or backlog items:

  1. In ALM Octane, in a Tests tab (Quality or Backlog module), click a test's link to open it.

  2. In Covered content, select the relevant backlog items.

  3. In Application modules, select the relevant application modules.

Manually assign multiple tests to application modules :

  1. In ALM Octane, in the Tests tab, select the tests and click Assign to Application Module.

  2. Select the relevant application modules.

Set up rules that automatically assign automated tests to application modules:

DevOps admin permissions are required.

In the DevOps > Test Assignment Rules setting page, you can set up rules that assign automated tests that match a filter you specify to specific application modules.

Tip: You can use the same rules to assign owners to automated tests, which can help accelerate problem resolution.

When you save a rule, all current and future automated tests that match the filter are assigned to the selected application modules and test owner. This includes tests that are currently in the system, as well as new automated tests that will be discovered in the future.

For details, see Create and manage test assignment rules.

You can also create test assignment rules from the Backlog or Quality modules. For details, see Automatically assign automated tests to application modules.

Back to top

Configure SCM Settings

DevOps admin permissions are required.

If your Jenkins or Bamboo server is set up to work with a Source Control Management (SCM) system, such as Git or Subversion (SVN), ALM Octane can help you track committed changes. See also Supported CI and SCM systems.

For details, see Track changes committed to your Source Control Management system.

See Integrate with your SCM system to learn about settings you can configure to gain more from this integration with your SCM system.

Analyze your build and release quality

After you create, configure, and run pipelines, you can Reflect your build, product, and release quality based on the collected information.

Analyze the product and release quality based on the automated test run results in ALM Octane's various dashboards, overview widgets, and grids. For details, see Track and analyze build, release, and product quality.

Analyze your build quality by learning more about the build runs and analyzing failed automated tests:

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

  • To view information about all the build runs of this pipeline and about changes made to the pipeline, click the pipeline ID to the left of the pipeline name.

    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 its details. For example:

Back to top