Share this page

# ALM Octane integrations overview

This topic lists the tools that ALM Octane integrates with at various stages of your application's lifecycle.

In this topic:

## 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.

Back to top

## Micro Focus Connect

Micro Focus Connect is the designated synchronization solution for ALM Octane. For instructions on working with Micro Focus Connect, see Micro Focus Connect Help Center.

When working with Micro Focus Connect, there is a wide range of connectors that can be used to synchronize third-party applications with ALM Octane, including ALM, Jira, Rally, and many more. For the full list of connectors available with Micro Focus Connect, see Micro Focus Connect Connectors.

Back to top

## IDE integrations

ALM Octane supports the following IDE integrations:

Integration | How?
--- | ---
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 Visual Studio Code (VS Code) editor.

For a feature support matrix, see Functionality supported by IDE integrations.

Back to top

## 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 changes committed to your Source Control Management 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
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 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.

Back to top

## Build automation: CI server integrations

ALM Octane incorporates data from your CI pipelines into your application delivery process, helping you analyze quality, progress, change impact, code coverage, and more. For details, see CI Pipelines.

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 (technical preview)
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.
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 a list of functionalities supported by each CI server integration, see Functionality supported by CI integrations.

Back to top

## Testing tool integrations

ALM Octane incorporates tests and results from various sources into the overall product and release data.

Integration | Details
--- | ---
Micro Focus testing tools: UFT One, UFT Developer, UFT Mobile, LoadRunner Professional, 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 flow (pipelines).
UFT One (Unified Functional Testing) | 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. See Set up UFT One integration and Run automated tests from ALM Octane.
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. Available with the following versions and later: ALM Octane 15.20.1 ALM/QC 15.5, 12.60 Patch 6 See Inject 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 we recommend that you use the ALM test run injection mechanism instead.) See Send automated test run results to ALM Octane.
Quality of Things (QoT) | On-premises 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 and edit manual tests in Sprinter.
Third-party testing tools and frameworks, such as Selenium, NUnit, JUnit, and TestNG. | Via pipelines, using an ALM Octane CI plugin. See Set up CI servers. You can also set up testing integrations that enable you to execute tests from ALM Octane test suites. See Trigger automated test runs in your testing framework.

Back to top

## 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 Micro Focus 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.

Back to top

## Integrations with Commercial Off the Shelf software (COTs)

ALM Octane integrates with the following COTs:

Integration | Details
--- | ---
ALM defect, requirement, and release synchronization | See Synchronization.
Jira defect and backlog synchronization | See Synchronization.
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 ALM Octane – 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 Micro Focus AppDelivery Marketplace page.

Back to top

## 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 Overview for developers.

Back to top

See also:

- DevOps integrations
- IDE integrations

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ValueEdge & ALM Octane Help Center ValueEdge ALM Octane Help 16.0.100-16.0.400 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: