Harness plug-in

Available in versions: 26.3 and later

The Harness plug‑in enables you to run performance tests and synchronize workspace scripts directly from a Harness CI/CD (continuous integration/continuous delivery) pipeline. This integration supports automated, end‑to‑end performance testing and workspace synchronization as part of your CI workflow.

Overview

The Harness plug‑in integrates Enterprise Performance Engineering capabilities into Harness CI/CD pipelines. The integration is delivered as a Docker container image that includes a Harness step definition. You can reference this step in pipeline‑as‑code or access it from the Harness user interface when a custom step is enabled.

With this plug‑in, you can:

  • Trigger performance tests on an Enterprise Performance Engineering server.

  • Monitor ongoing test execution.

  • Generate analysis or trend reports.

  • Retrieve report status.

  • Run preexisting tests or tests defined by YAML files stored in your Harness repository.

  • Synchronize scripts from your workspace to your project by using the WorkspaceSync action.

Prerequisites

The following are the prerequisites for setting up the Harness action.

  • Harness permissions. You must have a Harness account with permissions to create and modify CI/CD pipelines and to reference external container images.

  • Docker access. Harness must be able to access the required Docker image using either a Docker connector or public access to Docker Hub.

  • OpenText authentication. You must have an Enterprise Performance Engineering API token with permissions to trigger tests and retrieve test results.

  • Test configuration. You must have either:

    • Predefined test IDs in your OpenText Enterprise Performance Engineering installation, or

    • A YAML configuration file checked into your Harness repository.

Plug-in resources

For instructions on triggering tests from Harness and usage examples, see GitHub repository.

For details on running the Docker image container, see Docker Hub image.

The GitHub repository and Docker Hub documentation include examples for the ExecuteLreTest and WorkspaceSync actions.

Using the Custom Step in Harness

Harness supports adding a custom pipeline step, which allows the plug‑in to appear as a selectable step in the Harness user interface. This capability requires an organization‑level Harness account.

To build the custom step manually:

  1. Download or clone the following directory:

    https://github.com/MicroFocus/opentext-enterprise-performance-engineering-ci-plugin/tree/main/nodejs-opentext-plugin-step-for-harness

  2. Package its contents into a ZIP file.

  3. Upload the ZIP file to Harness as a custom step definition.

Note:  

  • The custom step is not available in the default Harness cloud project.

  • Default cloud environments do not currently support testing or enabling custom steps, so usage is limited to pipeline‑as‑code or directly referencing the Docker image.

Action inputs

For details on Action inputs, see the Inputs & Outputs (Configuration) section in the OpenText Enterprise Performance Engineering – CI/CD Plugin GitHub repository.

Most parameters match the plug-in documentation. When used as Action inputs, all parameters must be uppercase and prefixed with PLUGIN_.

Set PLUGIN_LRE_ACTION to ExecuteLreTest or WorkspaceSync.