# Integrations

### Integrations available: <a href="#integrations-available" id="integrations-available"></a>

* CI/CD integrations - Jenkins, TFS, Azure Devops
* Git integrations - All standard git service provider.
* Bug reports integrations - Jira.

### CI/CD integrations: <a href="#ci-cd-integrations" id="ci-cd-integrations"></a>

In order to integrate your CI/CD tool, you need to configure ‘CloudBeat CLI’ as a part of your build process.

Here’s a video on how to do it:

<https://www.youtube.com/watch?v=ky6NEvedQFc>

### Git integrations: <a href="#git-integrations" id="git-integrations"></a>

To sync with your Git service provider you need to provide the following:

* URL - the address to your git project
* Branch name - for example: ‘master’
* Name - your git username
* Password - your git password

This configuration needs to be done when first creating a [project](https://cloudbeat.atlassian.net/wiki/spaces/CBDOC/pages/220102667/Projects).

### Bug reports integrations: <a href="#bug-reports-integrations" id="bug-reports-integrations"></a>

When a test case is finished with status failed - you may integrate it with a bug report system such as ‘Jira’.

You need to do the following:

1. Go to your failed test results page by clicking it.
2. Select a failure reason from the drop down list on the top line of the test case.
3. On the top line you will have a ‘Jira’ button - click it.
4. Link the bug you opened in Jira in the ‘Link’ field.
5. Click ‘Add’ and the dialog will close.


---

# Agent Instructions: 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:

```
GET https://docs.cloudbeat.io/features/integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.