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.
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 |
|
|
|
|
|
|
|
|
|
| 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 |
|
|
|
|
|
|
|
|
|
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 tests from ALM Octane |
|
|
|
|
|
|
|
|
|
| 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) |
|
|
|
|
|
|
|
|
|
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 |
|
|
|
|
|
|
|
|
|
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 |
|
|
|
|
|
|
|
|
* The app service supports Azure DevOps Server (previously TFS). The extension integration supports Azure DevOps Server 2019 and later, and Azure DevOps Services.
See also:
