> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/quick-onboarding/adding-a-cd-provider/jenkins-pipeline.md).

# Jenkins Pipeline

**a. Resources > Providers**\
\
Click on the “Resources” tab from the left-hand menu. Select the Providers.

<figure><img src="/files/zMlloSS3hmhkP9u6tYGV" alt=""><figcaption></figcaption></figure>

**b. Create New CD Provider**

<figure><img src="/files/xSQSqkn9apAGQgBrPOCz" alt=""><figcaption></figcaption></figure>

The screen updates to a view showing available providers. Click on “Create a New Provider”. at the top right corner

**c. Select CD as a Provider**

<figure><img src="/files/11TVHmXZmrEoa5zDBX9K" alt=""><figcaption></figcaption></figure>

Select Continuous Deployment to connect with Jenkins

**d. Select Jenkins**

<figure><img src="/files/pxNh5e0G7FRPoTELeeUa" alt=""><figcaption></figcaption></figure>

Select the provider from which you want to integrate your CD provider onto Ozone. For now, let us go ahead with the Jenkins Pipeline

**e. Onboard Your Jenkins Provider**

<figure><img src="/files/D1QDT4dQkw0CrrLhcUO2" alt=""><figcaption></figcaption></figure>

Give a name, description, Jenkins URL, username, and personal access token to connect Jenkins as a provider. After filling in the details click on "Test my Integration"\
\
**f. Integration Successful** <br>

<figure><img src="/files/qkM6zwcazE31fpJyJHWG" alt=""><figcaption></figcaption></figure>

You can see the toaster message indicating the Integration is successful. Then click on Submit.

<figure><img src="/files/rrRMiiW2sZ0SHWajjGvE" alt=""><figcaption></figcaption></figure>

Your Jenkins provider will now be visible in the provider list view screen while navigating from the “Resources” tab in the menu.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ozone.one/ozone-end-user-guide/quick-onboarding/adding-a-cd-provider/jenkins-pipeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.