Share this page

# Integrations

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

In this topic:

## Secure connection

When working with integrations, configure OpenText Software Delivery Management with a secured TLS (SSL) connection. For instructions, see OpenText Software Delivery Management Secure Deployment and Configuration Guidelines.

Back to top

## Connect

Synchronize data from external sources through OpenText's synchronization tool. For details, see Connect Help Center.

Note: Use automated tools to migrate your OpenText Application Quality Management, Silk Central, and Jira projects to OpenText Software Delivery Management. For details, see Shift on the AppDelivery Marketplace.

Back to top

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

Back to top

## Source code management (SCM) integrations

By integrating your CI server with OpenText Software Delivery Management, 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
GitHub Actions | 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.

Back to top

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

Back to top

## 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: OpenText Functional Testing, OpenText Functional Testing for Developers, OpenText Functional Testing Lab for Mobile and Web, OpenText Core Performance Engineering, and OpenText Enterprise Performance Engineering | Use the Pipelines module to integrate with your CI server. OpenText Software Delivery Management receives testing tool test run results from the pipeline runs. See Automated testing.
OpenText Functional Testing | Set up OpenText Functional Testing integration without pipelines. The OpenText Functional Testing integration discovers OpenText Functional Testing tests and data tables stored in Git or SVN, enabling you to run the tests in test suites. See Set up OpenText Functional Testing integration and Run automated tests.
OpenText Application Quality Management test run injection | Integrate with OpenText Application Quality Management to automatically inject test sets and test runs from OpenText Application Quality Management to OpenText Software Delivery Management. See Inject test runs from OpenText Application Quality Management.
OpenText Application Quality Management test result tracking (offline) | Using the OpenText Application Quality Management Test Result Collection Tool. Note: We recommend using the OpenText Application Quality Management test run injection mechanism instead. See Receive automated test run results.
Quality of Things (QoT) | Use QoT to download planned manual runs and suite runs, run them offline, and upload test results to OpenText Software Delivery Management. See Quality of Things (QoT).
Sprinter | Run OpenText Software Delivery Management 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.

Back to top

## Security testing integrations

Track your security issues as defects.

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.

Back to top

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

Integrations with the following COTs are supported.

Integration | Details
--- | ---
Test management for Jira | The OpenText Software Delivery Management – 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 OpenText Software Delivery Management.
Slack | Add your OpenText Software Delivery Management 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.

Back to top

## Additional integrations using the REST API

Expand your integrations to applications of your choice by using the REST API.

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

Back to top

See also:

- DevOps integrations
- IDE integrations

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: