This topic lists the tools that ALM Octane integrates with at various stages of your application's lifecycle.
About ALM Octane integrations
Extend ALM Octane's capabilities by connecting to other systems you use in your release lifecycle. ALM Octane connects the dots from the various tools, providing comprehensive end-to-end control of the lifecycle.
Caution: When working with integrations, configure ALM Octane with a secured TLS (SSL) connection. For instructions, see ALM Octane Secure Deployment and Configuration Guidelines.
For details, see
ALM Octane supports the following IDE integrations:
|IntelliJ||See Work in IntelliJ IDEA.|
|Eclipse||See Work in Eclipse IDE.|
|Microsoft Visual Studio||See Work in the Microsoft Visual Studio IDE .|
|Microsoft Visual Studio Code||See Work in the Microsoft VS Code editor.|
For a feature support matrix, see Functionality supported by IDE integrations.
By integrating your CI server with ALM Octane, you can track changes committed to your Source Control Management system. For details, see Track commits to your SCM system.
ALM Octane imports SCM information via the integrated CI server.
Depending on the CI server you use, ALM Octane supports the following SCM systems:
|CI server||Supported SCM systems|
|Jenkins||Git, SVN, and limited support for other SCMs|
|Azure DevOps Server (TFS)||Git|
|Azure DevOps Services (VSTS)||Git, TFVC (Team Foundation version control)|
Note: ALM Octane supports any repository hosting services that are using one of the supported SCM systems. For example: GitHub, BitBucket, or GitLab.
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.
ALM Octane integrates with CI and CD servers to ensure automated build and deployment.
Build automation: CI server integration
ALM Octane incorporates data from your CI pipelines into the application delivery process, helping you analyze quality, progress, change impact, code coverage, and more. For details, see Pipelines.
The following table provides details on CI server integrations:
|CI server||Plugin location|
|Jenkins, TeamCity, Bamboo, TFS, GoCD||Plugins are available online from the CI server websites: Jenkins, TeamCity, Bamboo, TFS, GoCD|
The integration with ALM Octane is provided as part of the Application Automation Tools plugin.
For a list of 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, see the Application Automation Tools wiki page or Jenkins integration.
|Azure DevOps Server 2019 and later and Azure DevOps Services (VSTS)||
The app service supports Azure DevOps Server (previously TFS). The extension integration supports Azure DevOps Server 2019 and later, and Azure DevOps Services.
|GitLab||Standalone application ALM Octane GitLab CI service. The application uses the GitLab API to get events from GitLab and push them to ALM Octane.|
|GitHub Actions||See alm-octane-github-actions-integration.|
|PulseUno||No plugin is required – the CI server integration is a core part of PulseUno.|
|Other CI servers||For CI servers not listed above, build your own plugin in Java using the CI Plugin SDK for ALM Octane available on GitHub.|
For functionality supported by CI server integration, see Functionality supported by CI integrations.
Deployment automation: CD server integrations
The CD server integration enables you to automatically run Deployment Automation application processes via release process auto actions. For details on auto actions, see Create a release process.
Technical preview: The Deployment Automation integration is provided as a technical preview. It may require a separate license in the future.
ALM Octane incorporates tests and results from various sources into the overall product and release data.
OpenText testing tools:
UFT One, UFT Developer, Digital Lab, LoadRunner Cloud, and LoadRunner Enterprise
Use the Pipelines module in ALM Octane and integrate with your CI server.
ALM Octane receives testing tool test run results from the pipeline runs.
UFT One (UFT One)
Set up UFT One integration without pipelines.
ALM Octane discovers UFT One tests and data tables stored in Git or SVN, enabling you to run the tests in ALM Octane test suites.
|ALM test run injection||
Integrate between ALM Octane and ALM/QC to automatically inject test sets and test runs from ALM/QC to ALM Octane.
|ALM test result tracking (offline)||
Via the ALM Test Result Collection Tool. (This is still supported, but you should better use the ALM test run injection mechanism instead.)
|Quality of Things (QoT)||
ALM Octane users can use QoT to download planned manual runs and suite runs, run them offline, and upload test results to ALM Octane.
Run ALM Octane manual tests in Sprinter.
|Third-party testing tools and frameworks, such as Selenium, NUnit, JUnit, and TestNG.|
Track your security issues as defects in ALM Octane:
|Set up an integration with Fortify, enabling each ALM Octane pipeline run to display the new security vulnerabilities found on that run. For details, see Set up an integration with Fortify.|
The Fortify BugTracker Utility enables you to open security defects on ALM Octane directly from Fortify. For details, see the Fortify Marketplace page.
|Set up an integration with SonarQube, enabling each ALM Octane pipeline run to display the new security vulnerabilities found on that run. For details, see Set up an integration with SonarQube.|
ALM Octane integrates with the following COTs:
Test management for Jira
The ALM Octane – Test Management for Jira plugin provides Jira users test coverage and status information directly on native Jira Epics, Stories, Issues or custom types.
|Project and Portfolio Management (PPM)||See Integrations with ALM Octane.|
|Slack||Add your ALM Octane workspace to a Slack workspace and open Slack channels from within backlog items or pipeline run failures. See Set up a Slack integration.|
|Teams||You can share an entity and comment on it via a Microsoft Teams channel. For details, see Discuss on Microsoft Teams.|
|Third-party applications||See the OpenText AppDelivery Marketplace page.|
Expand your integrations to applications of your choice by using ALM Octane's REST API.
|Other third-party applications or CI servers||
REST API, OData, and SDKs. For details, see Developer options.