Share this page

# Functionality supported by CI integrations

Integrating ALM Octane with a CI server enables varied functionality.

The sections below specify the functionality provided by each CI server integration, when using the latest version of the plugin.

In this topic:

## Pipelines and builds

The following table provides the functionality per CI server:

Functionality | Jenkins | PulseUno | Bamboo | TeamCity | GoCD | GitLab | Azure DevOps app service | Azure DevOps extension integration | GitHub Actions
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Collect pipeline step results |  |  |  |  |  |  |  |  |
Run pipeline from ALM Octane |  |  |  |  |  |  |  |  |
Run pipeline with parameters |  |  |  |  |  |  |  |  |
Hierarchy in Topology |  |  |  |  |  |  |  |  |
Multi-branch pipeline |  |  |  |  |  |  |  |  | Version 24.3 and later:
Configure instance ID in CI plugin |  |  |  |  |  |  |  |  |
Collect failed build logs, configure automatic build failure classification |  |  |  |  |  |  |  |  |
Multiple spaces |  |  |  |  |  |  |  |  |
Trigger a CI job from a release process auto action |  |  |  |  |  |  |  |  |

Back to top

## Test automation

The following table provides the functionality per CI server:

Functionality | Jenkins | PulseUno | Bamboo | TeamCity | GoCD | GitLab | Azure DevOps app service | Azure DevOps extension integration | GitHub Actions
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Collect test run results |  |  |  |  |  |  |  |  |
Ignore test run results for specific pipeline steps |  |  |  |  |  |  |  |  |
Automatically set a test run's testing tool / test type |  |  |  |  |  |  |  |  |
Run on-demand automated test types from ALM Octane using preconfigured frameworks. (See plugin readmes for supported frameworks) |  |  |  |  |  |  |  |  |
Run on-demand automated tests from ALM Octane using custom frameworks |  |  |  |  |  |  |  |  |
Run UFT One from ALM Octane |  |  |  |  |  |  |  |  |
Automated Gherkin Cucumber test injection |  |  |  |  |  |  |  |  |
Automated Gherkin JBehave test injection |  |  |  |  |  |  |  |  |
Automated Performance Test injection (LRC, LRE) |  |  |  |  |  |  |  |  |
Automated Performance Test injection with failure insights (LRC) |  |  |  |  |  |  |  |  |

Back to top

## SCM

The following table provides the functionality per CI server:

Functionality | Jenkins | PulseUno | Bamboo | TeamCity | GoCD | GitLab | Azure DevOps app service | Azure DevOps extension integration | GitHub Actions
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Collect SCM commit messages |  |  |  |  |  |  |  |  |
List the files in a commit |  |  |  |  |  |  |  |  |
Understand the type of file change in a commit |  |  |  |  |  |  |  |  |
Show branch details on backlog items |  |  |  |  |  |  |  |  |
Show pull request details on backlog items |  |  |  |  |  |  |  |  |

Back to top

## Code coverage and Security

The following table provides the functionality per CI server:

Functionality | Jenkins | PulseUno | Bamboo | TeamCity | GoCD | GitLab | Azure DevOps app service | Azure DevOps extension integration
--- | --- | --- | --- | --- | --- | --- | --- | ---
Collect code coverage reports |  |  |  |  |  |  |  |
Track security vulnerabilities |  |  |  |  |  |  |  |

Back to top

See also:

- Set up CI/CD integration
- CI server auto actions
- Integrations overview
- Trigger on-demand automated test runs
- Analyze build failures

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ALM Octane Help Center ALM Octane Help 23.4-24.3 All View Local Help Center View Online Help Center Version: