CI server integration flow

The following flow describes how to collect information from your CI server and use it to measure your release and product quality, and to follow your build progress.

In this topic:

Overview

Integration with your CI/CD processes enables you to do the following:

• Collect data from your CI server.
• Connect the CI data to the application modules and backlog items.
• Reflect the product quality in dashboards and grids, based on the automated test run results.

Back to top

Step 1: Collect data from your CI server

Install and configure the Application Automation Tools plugin or the Application Automation Tools Jenkins plugin on your CI server, and create pipelines in OpenText Core Software Delivery Platform.

The pipelines collect build and test run results, as well as SCM data and code coverage reports from your CI server. For more detail on what you can do with pipelines, see Pipelines.

Alternatively, use the Test Result Collection Tools to send your automated test run results. For details, see Push test results stored externally.

Based on the collected test run results, automated test and test run entities are created. For details, see Create automated tests.

Back to top

Step 2: Connect the CI data to entities

Assign tests to application modules, backlog items, and users. You can assign items manually or set up rules to automatically assign automated tests to specific application modules and test owners. For details on application modules and the backlog tree, see Build the application module tree and Build the backlog.

The automated tests results are then incorporated into your product and release quality reports.

You can then use these results to analyze the quality of your product or release in dashboards and grids.

Back to top

Step 3: View integrated data

After you create, configure, and run pipelines, the collected information reflects your build, product, and release quality.

You can review the information in the following ways.

Method	Location
View graphs and charts that reflect your product and release quality based on automated test run results. Use predefined widgets from the widget gallery, or design your own.	In the Dashboard module, and in the Overview tab of other modules.
Study your pipeline results, including code changes and failures to which they may be related. If available, you can also see code coverage reports and newly discovered security vulnerabilities.	In the Pipelines module.

Back to top

Next steps:

• Set up CI/CD integration
• Create and configure pipelines
• Run pipelines
• Assign tests to application modules and backlog items
• Set up your SCM system