Share this page

# Publish chain results to OpenText Software Delivery Management

You can integrate a PulseUno chain with an OpenText Software Delivery Management pipeline and send chain run results to OpenText Software Delivery Management.

Tip: A chain that publishes results to OpenText Software Delivery Management can also integrate with an OpenText Software Delivery Management release process. When you define actions for your release process in OpenText Software Delivery Management, add a CI server auto action that will run the chain. For details about releases and CI server auto actions, see the OpenText Software Delivery Management help.

In this topic:

## Pipeline integration steps

In a working integration, you can run a PulseUno chain that publishes its results to OpenText Software Delivery Management, and you can view the results as an OpenText Software Delivery Management pipeline. The chain acts as a root job to start the OpenText Software Delivery Management pipeline.

To integrate a PulseUno chain with an OpenText Software Delivery Management pipeline, complete the following steps.

Step | Description
--- | ---
Step 1 | In PulseUno: Connect to an OpenText Software Delivery Management instance. See Connect to OpenText Software Delivery Management.
Step 2 | In PulseUno: Enable the relevant product or Git repository to use the OpenText Software Delivery Management connection. See Enable OpenText Software Delivery Management connection.
Step 3 | In PulseUno: Set up a chain to publish chain run results to OpenText Software Delivery Management. See Create a chain to publish to OpenText Software Delivery Management.
Step 4 | In OpenText Software Delivery Management: Add a PulseUno CI server.
Step 5 | In OpenText Software Delivery Management: Create a pipeline that runs on the PulseUno CI server and uses the chain you configured for OpenText Software Delivery Management.

For details on how to complete the tasks in OpenText Software Delivery Management, see the OpenText Software Delivery Management help.

Back to top

## Enable OpenText Software Delivery Management connection

Note: If PulseUno is already configured to use OpenText Software Delivery Management for requests, the OpenText Software Delivery Management connection is enabled automatically. For details, see Enable OpenText Software Delivery Management requests.

After you connect an OpenText Software Delivery Management instance, enable your product or Git repository to use this connection for the pipeline integration.

Note: Administrator or owner permissions required.

To enable the OpenText Software Delivery Management connection:

1. In PulseUno, on the top navigation bar, select the relevant space from the spaces list.

2. On the Products page, open the product or Git repository from which to publish to OpenText Software Delivery Management.

3. On the sidebar, select Settings > Integrations.

4. On the Integrations page, in the OpenText Software Delivery Management section, select the connection and enter the ID of the relevant OpenText Software Delivery Management workspace.

   Note: If you have enabled an OpenText Software Delivery Management instance as a request provider, PulseUno automatically uses the same connection for the pipeline. For details, see Enable OpenText Software Delivery Management requests.

5. Click Save.

After enabling the connection, set up a chain to publish results to OpenText Software Delivery Management.

Back to top

## Create a chain to publish to OpenText Software Delivery Management

After you create and enable an OpenText Software Delivery Management connection, set up a chain to send results to OpenText Software Delivery Management.

You can also pass custom output properties to OpenText Software Delivery Management. For example, if a chain produces measurements, you can publish them to OpenText Software Delivery Management as output properties.

Note: Administrator, owner, or maintainer permissions required.

To configure a chain to publish to OpenText Software Delivery Management:

1. In PulseUno, on the top navigation bar, select the relevant space from the spaces list.

2. On the Products page, open the product or Git repository from which to publish to OpenText Software Delivery Management.

3. On the sidebar, select Chains.

4. Open the chain you want to use for the integration, and click Edit.

   Or create a new chain, as described in Create chains.

   Tip: To create a test runner chain that pushes unit test results to OpenText Software Delivery Management and enables you to run a tests pipeline from OpenText Software Delivery Management, use the Maven, Gradle, or UFT One plugins. For details on how to integrate OpenText Functional Testing testing between PulseUno and OpenText Software Delivery Management, see Run OpenText Functional Testing tests from OpenText Software Delivery Management.

5. In the Steps tab, click Add step to chain .

6. From the Add Step list, add the Publish results to OpenText Software Delivery Management plugin as the last step on the chain.

7. Click the step and enter the following configuration details:

   Field | Description
   --- | ---
   Title | Enter a name for the chain step, or use the default name.
   Comment on work items associated with the chain run | By default, if the chain run was successful or unstable, PulseUno publishes the link to the chain run as a comment on all related OpenText Software Delivery Management work items. This way, after running a build to merge a certain feature to the main branch, you can check the associated work items in OpenText Software Delivery Management and instantly know which build delivered the feature. If you do not want to publish the comment, clear the option Publish a link to last completed chain run. To publish the comment even if the chain run fails, clear the option Add the comment only for success and unstable chain states.
   Logs | By default, PulseUno publishes build logs to an OpenText Software Delivery Management pipeline only when the chain step fails. To send build logs on every run, clear the option Only send log when chain step fails. The default log size limit is 150 MB. If the log size is larger, PulseUno truncates the log file, removing the earliest entries. Note: As an administrator, you can change the log size limit by editing the octane.pipeline.log.limit.size.mb property in Administration > System Properties. To view the log in OpenText Software Delivery Management, open the Logs tab of the associated pipeline job.
   Metrics to publish as output properties | To publish custom output properties, specify key=value pairs, where value is a metric or built-in variable. Enter each pair on a new line using the following syntax: KEY={{metric.<measurement name>}} KEY={{pulse.<variable name>}} For example: BUILD_DISPLAY_NAME={{pulse.chain_full_name}} BUILD_URL={{pulse.chain_run_url}} BUILD_TAG={{pulse.changeset_id}} For details about available built-in variables, see Use variables in chains. To publish the state of the chain run, use the {{chain.status}} variable. You can pass metrics from other chain steps. If multiple steps produce the same measurement, specify the step name (copy the name from the Title field): {{metric.<step name>.<measurement name>}} For example, to publish the finding count from the Script 01 step, enter: FINDING_COUNT={{metric.script 01.finding count}} or FINDING_COUNT={{metric.script_01.finding_count}} Step and measurement names are not case-sensitive. Spaces are automatically converted to underscores. If multiple chain steps produce the same measurement, and the step name is not specified, PulseUno uses the value from the step that runs last. For example, if the same metric is defined in steps 1, 2, and 3, the metric from step 3 is converted to an output property.
   Control options | (Optional) Define the control options for the plugin step: Enable step. By default, the step is enabled to run. Clear this option if you need to deactivate the step. Deactivated steps are skipped when the chain runs. Fail the step. Specify the conditions for failing the step, such as unit test failures, findings criteria, and/or console log entries. Mark step as unstable. Specify the conditions for making the step unstable, such as unit test failures, findings criteria, and/or console log entries.
   Output variables | (Optional) Specify the output variables to be passed to other steps down the chain. For details, see Publish output variables.

8. Test runner chains only: If you use this chain to run unit tests and push test results to OpenText Software Delivery Management, add the TestsToRun variable on the chain. Leave the value empty.

   You must set the testsToRun variable so that OpenText Software Delivery Management can send a list of tests to run in PulseUno. For details on how to define variables, see Add chain variables.

9. To specify the schedule or the conditions for running the chain, select the Triggers tab and set the Run chain option. For details, see Schedule chain runs.

10. Click Save & Continue.

You can run the chain after you finish configuring the integration with OpenText Software Delivery Management.

When the chain is run, PulseUno automatically creates a CI server and pipeline for the chain in OpenText Software Delivery Management, if the API key used for the connection is associated with the required permissions in OpenText Software Delivery Management.

Back to top

See also:

- Run OpenText Functional Testing tests from OpenText Software Delivery Management
- Synchronize with OpenText Software Delivery Management work items
- View chain runs

https://admhelp.microfocus.com PulseUno 8942
Tips to improve your search results... PulseUno Help Center PulseUno Help 24.2 - 25.2 All View Local Help Center View Online Help Center Version: