Integrations

Integrations are available for different stages of your development and quality lifecycle.

Integration Hub

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 OpenText Core Software Delivery Platform. 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 IDE integrations.

Source code management (SCM) integrations

By integrating your CI server with OpenText Core Software Delivery Platform, 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: Any repository hosting services that use one of the supported SCM systems is supported. 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

Data from your CI pipelines is incorporated into the application delivery process, helping you analyze quality, progress, change impact, code coverage, and more. For details, see Pipelines.

For a list of available CI server plugins and their locations, see Install the plugin.

For functionality supported by CI server integration, see 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, see Release processes.

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 to integrate with your CI server. OpenText Core Software Delivery Platform 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 test suites. See Set up UFT One integration and Run automated tests.
ALM test run injection	Integrate with ALM/QC to automatically inject test sets and test runs from ALM/QC to OpenText Core Software Delivery Platform. See Inject test runs from ALM/QC.
ALM test result tracking (offline)	Using the ALM Test Result Collection Tool. Note: We recommend using the ALM test run injection mechanism instead. See Receive automated test run results.
Quality of Things (QoT)	User QoT to download planned manual runs and suite runs, run them offline, and upload test results to OpenText Core Software Delivery Platform. See Quality of Things (QoT).
Sprinter	Run OpenText Core Software Delivery Platform manual tests in Sprinter. See Run manual tests in Sprinter.
Third-party testing tools and frameworks, such as Selenium, NUnit, JUnit, and TestNG.	Through pipelines, using a CI plugin. See Set up CI/CD integration. You can also set up testing integrations that enable you to run tests on-demand from test suites. See Trigger on-demand automated test runs.

Security testing integrations

Track your security issues as defects in OpenText Core Software Delivery Platform.

Integration	Details
Fortify	Set up an integration with Fortify, enabling each pipeline run to display the new security vulnerabilities found on that run. For details, see Fortify integration.
Fortify	The Fortify BugTracker Utility enables you to open security defects directly from Fortify. For details, see the Fortify Marketplace page.
SonarQube	Set up an integration with SonarQube, enabling each pipeline run to display the new security vulnerabilities found on that run. For details, see SonarQube integration.

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

Integrations with the following COTs are supported.

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 OpenText Core Software Delivery Platform 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 OpenText Core Software Delivery Platform's REST API.

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