Pipelines: Integrate with your CI server
ALM Octane integrates with CI servers so you can:
View build pipelines.
Check build quality.
Incorporate automated testing results into your release and product quality analysis.
Track changes committed to the SCM system integrated with your CI server.
See also Supported CI and SCM systems.
After you set up ALM Octane to integrate with your continuous integration (CI) server, you can create pipelines in ALM Octane.
Pipelines graphically represent the flow of your CI server jobs. If you are working with Jenkins or Bamboo, you can also see the hierarchy of the jobs in the flow.
Note: Creating, configuring, and deleting pipelines require workspace admin or DevOps admin permissions in the relevant workspace.
|Collect pipeline run and automated test run results from the CI server.||
Pipelines > Pipelines tab
|View a graphical representation of the pipeline flow, the various steps' status, a summary of the test run statistics, and more.|
|Configure test properties and environment data on pipeline steps that run automated tests.||
Pipelines > Pipelines tab
You can later filter the test run results based on this data, in the Tests tab (Quality or Backlog module).
|Include automated test run results in product and release quality analysis.||Dashboards and Overviews throughout ALM Octane||Requires assigning automated tests to application modules (Settings > DevOps > Test Assignment Rules) or backlog items.|
|Track commits associated with specific build runs and specific user stories and defects.||
Inside a pipeline run or a story.
Additional customization in Settings > DevOps page.
Requires working with a Jenkins or Bamboo CI server that integrates with an SCM system.
When you add a pipeline, you specify a job on the CI server to use for the root of the pipeline. ALM Octane then follows your pipeline structure, and builds a graphic representation of the pipeline.
The pipeline's structure is dynamic. If additional jobs are added in the CI server after you created the pipeline in ALM Octane, these steps are added the next time the pipeline runs.
If the pipeline runs jobs that ALM Octane did not initially detect as part of the pipeline, they are added to the pipeline during the run.
A step that is no longer run as part of the pipeline flow is not removed from the pipeline. It is colored gray to indicate it is not current. The more times the pipeline runs without running this step, the less vividly the step appears in the pipeline.
When you first added the pipeline, ALM Octane discovered steps A and B and displayed them in the pipeline.
- When the pipeline ran on the CI server for the first time, step B ran step C, so ALM Octane added step C to the pipeline.
- The next time the pipeline ran on the CI server, step B ran step D instead of step C. ALM Octane added step D to the pipeline. Step C remained in the pipeline, but is displayed in gray, indicating that it did not run this time.
- If, in a subsequent run, step C runs instead of step D, step C will be displayed regularly in the pipeline, and step D will be gray.
In ALM Octane, you can see the flow of steps in the CI server, including which steps run in sequence and which steps run as parts of other steps.
You can expand and collapse steps to see sub-steps.
While running a pipeline, you can see the build number, the last run date, the run status, and the duration of the run. If something failed or is taking too long, you can investigate what the problem is.