> 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/running-the-pipeline-in-harness.md).
# Running the Pipeline in Harness
1. Paste the Code Snippet that was copied from Avo Assure into the execution shell script
2. Click **Run** button.
3. Click **Run Pipeline** to trigger the pipeline with the set parameters.
4. Once the pipeline is triggered, the execution starts in the command prompt, and two links are displayed in the console:
**A. reportLink**
**B. runningStatusLink**
5. Steps after clicking **reportLink** and **runningStatusLink:**
{% tabs %}
{% tab title="A. reportLink" %}
#### Once after clicking ReportLink, then it will navigate to the Avo Assure Login page.
1. Provide Username and Password in their respective filed.
2. Click login button, it will directly navigate to the Report tab in Avo Assure.
{% hint style="info" %}
**Note:** Select the recently trigged Execution list.
{% endhint %}
3. In the right pane, Click Test Case Details button. Run Details pop up window appears.
4. Select View Report icon to navigate to Result Summary window.
5. Expand Test Step Group and see the Execution result.
{% endtab %}
{% tab title="B. runningStatusLink" %}
1. After clicking the **runningStatusLink**, it opens a UI that displays the live execution status. (e.g., InProgress, Queued and Completed)
{% endtab %}
{% endtabs %}
---
# 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/running-the-pipeline-in-harness.md?ask=&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.
