> 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-docker/devops-window-in-avo-assure.md).

# DevOps Window in Avo Assure

**Step-by-step process to navigate to DevOps window in Avo Assure:**

1. Select required **Project** from **Projects** section.
2. Click **Design Studio**.
3. Navigate to **Execution** tab present in Design Studio window, then select **Execution List folder**.
4. Click **DevOps** button, to bring up DevOps window.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FovHGXKuindDJkrMmpUyP%2Fimage.png?alt=media&amp;token=59132fe5-3923-4059-9237-2b4ea5d8b6b7" alt=""><figcaption></figcaption></figure>

5. Select **Cloud Execution** radio button.
6. Increase number of Parallel count that user want to execute the Execution list that many time.
7. In the Environment dropdown user can see two options:
   1. **Docker**
   2. [**Harness**](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/devops-integration/cloud-execution/ci-cd-harness.md)

### **a. Steps by selecting Docker as Environment**

1. Click **first** **Copy** icon to copy the code snippet, which contains the container image of the **Avo Assure Clien**t.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FqXU6Xlia8cIaN34IItUo%2Fimage.png?alt=media&amp;token=de4a395d-2431-4354-89b9-6063bb433706" alt=""><figcaption></figcaption></figure>

2. Click **second Copy** icon to copy the code snipped which is contains the **Execution list** detail&#x73;**.**

{% hint style="info" %}
**Note:** Copy both code snippet and paste them in Notepad for use while triggering the execution list on cloud infrastructure.
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F3paJY5XuCR5RYyCU5Lqb%2Fimage.png?alt=media&amp;token=f03be48f-7aeb-4851-8955-80c68037f8d4" alt=""><figcaption></figcaption></figure>


---

# 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-docker/devops-window-in-avo-assure.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.
