ALM Octane product integrations

Configure ALM Octane to integrate with your CI and SCM systems, existing ALM projects, and software testing tools. Alternatively, use ALM Octane's API to integrate with applications of your choice.

Available integrations

The following table lists the available ALM Octane integrations:

Integration How?
ALM defect, requirement, and release synchronization (SaaS only)

ALM Octane Synchronizer

See Synchronize ALM Octane with ALM.

ALM test result tracking

ALM Test Result Collection Tool

See Send automated test run results to ALM Octane.

HPE Project and Portfolio Management (PPM) See Enabling Agile Projects Portlets for ALM Octane.

CI servers

HPE ALM Octane CI plugin.

For other CI servers, build your own plugin in Java using the CI Plugin SDK for ALM Octane available on GitHub.

See Pipelines: CI server & SCM system integration.

Source Code Management (SCM) systems: Git, SVN, and others

Via the CI server integration, using an HPE ALM Octane CI plugin.

See Track changes committed to your Source Control Management system.

HPE testing tools: LeanFT, UFT, LoadRunner, StormRunner

Via an automation or CI server, using an HPE ALM Octane CI plugin.

See Configure steps: Define test and test run information and View detailed test run results from external testing tools.

Integrated development environments (IDEs)

Work with ALM Octane directly within your IDE.

Currently, the IntelliJ IDEA IDE is supported.

For details, see Work in IntelliJ IDEA.


Add your ALM Octane workspace to a Slack team and open Slack channels from within backlog items.

See Set up Slack integration.

Other third-party applications or CI servers


See the ALM Octane Developer Guide.

Third-party applications See the HPE AppDelivery Marketplace page.

Back to top

Supported CI and SCM systems

Supported CI servers

The following CI servers are supported by the HPE ALM Octane CI plugins:

  • Jenkins version 1.580.2 or later

  • CloudBees Jenkins Enterprise version 15.11 or later, with CloudBees Jenkins Operations Center version 1.8 or later

  • TeamCity CI server version 9.1.6

  • Bamboo 5.13 or later

Required and supported Jenkins plugins

The table below lists the plugins that must be installed on the Jenkins server to enable ALM Octane integration, as well as plugins that are supported by the ALM Octane integration but not required.

Plugin Required / Supported
JQuery Plugin 1.7.2-1 or later Required to enable the integration.
A plugin that enables publishing test results. For example, JUnit Plugin 1.10 or later, NUnit plugin, and so on. Required to enable ALM Octane to collect your automated test results.

Pipeline Plugin (enabling Pipeline as Code)

Supported but not required

Note: ALM Octane creates a single pipeline step for each Jenkins job. Steps and stages inside a job are not recognized.

MultiJob Plugin 1.15 or later

Supported but not required

Maven Plugin 2.5 or later

Parameterized Trigger Plugin 2.25 or later

Matrix Job Plugin 1.4 or later

Note: ALM Octane can display a pipeline's structure only if it is built using one of the following: 

  • The built-in Jenkins upstream/downstream mechanism
  • The Multijob plugin
  • The Parameterized plugin

Supported SCM systems

ALM Octane imports SCM information via the integrated CI server.

Depending on the CI server you use, ALM Octane supports the following SCM systems:

Jenkins Any SCM system supported by Jenkins
Bamboo Git, SVN
TeamCity Git, SVN

The following functionality is available only if you use Git or SVN:

  • Repository information for commits.

  • Links to diff and file repository viewers for changed files.

Back to top