> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/devops-and-ci-cd.md).

# DevOps and CI/CD

This category covers source control, pipeline, and infrastructure-as-code platforms. These tools send alerts to ITOC360 when builds fail, deployments break, or critical pipeline events occur — ensuring the responsible engineer is notified before an issue reaches production.

***

### Integrations in this category

| Integration         | What it monitors                                                  | Alert delivery |
| ------------------- | ----------------------------------------------------------------- | -------------- |
| **ArgoCD**          | GitOps deployment health, sync failures, application degradations | Webhook        |
| **Azure DevOps**    | Build and release pipeline failures, work item events             | Webhook        |
| **GitHub**          | Workflow run failures, security advisories, repository events     | Webhook        |
| **GitLab**          | CI/CD pipeline failures, deployment events, security findings     | Webhook        |
| **Jenkins**         | Build job failures, pipeline stage errors                         | Webhook        |
| **Terraform Cloud** | Run failures, plan errors, workspace events                       | Webhook        |

***

### How it works

CI/CD and DevOps tools emit events at every stage of the software delivery lifecycle. When a pipeline fails, a deployment is rejected, or a security advisory is published, the tool sends an event payload to your ITOC360 Source webhook URL. ITOC360 parses the event, matches it against your escalation policies, and notifies the on-call engineer responsible for that pipeline or repository.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management > Sources**, create a Source, and paste the webhook URL into your tool's webhook or notification settings.
{% endhint %}

***

### Get started


---

# 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.itoc360.com/integrations/inbound-integrations/devops-and-ci-cd.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.