Integrations overview

This topic lists the tools that ALM Octane integrates with at various stages of your development and quality 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.

Connect

Synchronize data from external sources through OpenText's synchronization tool.

For details, see Connect Help Center.

Note: Use automated tools to migrate your ALM/QC, Silk Central and Jira projects to ALM Octane. For details, see Shift on the AppDelivery Marketplace.

IDE integrations

The following IDE integrations are supported:

Integration	Details
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.

Source code management (SCM) 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.

SCM information is imported via the integrated CI server.

Depending on the CI server you use, the following SCM systems are supported:

CI server	Supported SCM systems
Jenkins	Git, SVN, and limited support for other SCMs
Bamboo	Git, SVN
TeamCity	Git, SVN
Azure DevOps Server (TFS)	Git
GoCD	Git
GitLab	Git
Azure DevOps Services (VSTS)	Git, TFVC (Team Foundation version control)

Note: ALM Octane supports any repository hosting services that use 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.

CI and CD server integrations

The integration with CI and CD servers ensures 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
Jenkins	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)	ALM Octane Integration Extension 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.

Testing tool integrations

The following testing tool integrations are available. These integrations enable you to incorporate tests and results from various sources into the overall product and release data.

Integration	Details
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. See Automated testing.
UFT One (UFT One)	Set up UFT One integration without pipelines. The UFT One integration discovers UFT One tests and data tables stored in Git or SVN, enabling you to run the tests in ALM Octane test suites. See Set up UFT One integration and Run automated tests.
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. See Inject test runs from ALM/QC to ALM Octane.
ALM test result tracking (offline)	Using the ALM Test Result Collection Tool. Note: It is recommended to use the ALM test run injection mechanism instead.) See Send automated test run results to ALM Octane.
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. See Quality of Things (QoT).
Sprinter	Run ALM Octane manual tests in Sprinter. See Run manual tests in Sprinter.
Third-party testing tools and frameworks, such as Selenium, NUnit, JUnit, and TestNG.	Via pipelines, using an Application Automation Tools plugin. See Set up CI/CD integration. You can also set up testing integrations that enable you to execute tests on-demand from ALM Octane test suites. See Trigger on-demand automated test runs.

Security testing integrations

Track your security issues as defects in ALM Octane:

Integration	Details
Fortify	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.
Fortify	The Fortify BugTracker Utility enables you to open security defects on ALM Octane directly from Fortify. For details, see the Fortify Marketplace page.
SonarQube	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.

Integrations with commercial off-the-shelf software (COTs)

ALM Octane integrates with the following COTs:

Integration	Details
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. See Test Management for Jira plugin.
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.

Additional integrations using the REST API

Expand your integrations to applications of your choice by using ALM Octane's REST API.

Integration	Details
Other third-party applications or CI servers	REST API, OData, and SDKs. For details, see Developer options.