> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness.md).

# CI/CD Harness

## What is Delegate in Harness?

In Avo Assure, the Harness delegate is a custom container. This delegate acts as the communication bridge between the Harness environment and the Avo Assure Client. It enables Harness pipelines to trigger and manage Avo Assure test executions without requiring a local Avo Assure client installation and configuration in our system. The delegate must be active and connected inside the Harness environment for executions to run successfully.

## Usage

In Avo Assure, CI CD with Harness works by using the custom delegate image within the Harness pipeline. When a pipeline is triggered, the delegate establishes communication with the Harness environment and initiates the test execution request. It then connects with the Avo Assure Client running as a containerized image to execute the required Web tests against the application under test. After the execution is completed, the results are sent back through the delegate and made available within Harness for reporting and validation. This setup ensures integration of Avo Assure test execution into Harness pipelines, providing scalable and consistent automation as part of the CI/CD process.

### This document includes:

[Prerequisites](/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness/prerequisites.md)

Prerequisites for CI/CD Harness 

[DevOps windows in Avo Assure](/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness/devops-window-in-avo-assure.md)

Steps to copy DevOps URL & DevOps Request Body in Avo Assure

[Running the Pipeline in Harness](/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness/running-the-pipeline-in-harness.md)

Steps to run the pipeline in harness


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.