Pipelines: CI server & SCM system integration
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 represent the flow of your CI server jobs. If you are working with Jenkins or Bamboo, the graphical representation of the pipeline also shows 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 summary of the pipeline run details, test run statistics, a graphical representation of the pipeline steps' flow, and more.|
|Configure test properties and environment data on pipeline steps that run automated tests.||
Inside a pipeline
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.||
Pipelines > Pipelines tab, Team Backlog, and inside stories or pipeline runs.
Additional customization in Settings > DevOps page.
Requires working with a 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 visual 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.
In both cases, the new steps are visible the next time you open the pipeline.
In ALM Octane, in the Pipelines module, you can see all the pipelines that are being tracked, and filter to see the ones that interest you.
After a pipeline runs ALM Octane displays information about the pipeline run status, its run history, related code changes, affected application modules, and more. You can also find analytic information about failed tests and tools to help you analyze failures.