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

# Snyk CI/CDs

How to integrate Snyk into CI/CD pipelines, with the Snyk CLI recommended for flexibility

Snyk integrates with continuous integration and continuous delivery (CI/CD) pipelines so you can fail a build, or report on it, when a scan finds issues.

{% hint style="info" %}
Snyk recommends using the CLI for CI/CD integrations for the following reasons:

* You have the flexibility to test in-progress features of the CLI by using the preview channel.
* The CLI provides feature-rich stable releases at a regular cadence.
* With the CLI, you have options to extend use cases as you deploy Snyk at scale

For more information, see the [Snyk CLI repository](https://github.com/snyk/cli).
{% endhint %}

{% hint style="info" %}
**Snyk Secrets support**

Snyk Secrets does not support CI/CD plugin integrations. For CI/CD-time secret scanning, use [Secrets scanning in the Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-secrets/secrets-scanning-in-the-snyk-cli) directly in your pipeline.
{% endhint %}

## Adopting a CI/CD integration

When you decide to use a CI/CD integration, you typically adopt the integration in stages, initially selecting a deployment method and the implementing strategies for the code you are scanning. For details, see [Snyk CI/CD Integration deployment and strategies](https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/snyk-ci-cd-integration-deployment-and-strategies).

For detailed information, see the pages for the integration you are using:

* [AWS CodePipeline integration with CodeBuild](/developer-tools/integrations/snyk-ci-cd-integrations/aws-codepipeline-integration-by-adding-a-snyk-scan-stage.md)
* [Azure Pipelines integration](/developer-tools/integrations/snyk-ci-cd-integrations/azure-pipelines-integration.md)
* [Bitbucket Pipelines integration](/developer-tools/integrations/snyk-ci-cd-integrations/bitbucket-pipelines-integration-using-a-snyk-pipe/bitbucket-pipelines-integration-how-it-works.md)
* [CircleCI integration](/developer-tools/integrations/snyk-ci-cd-integrations/circleci-integration-using-a-snyk-orb.md)
* [GitHub Actions integration](/developer-tools/integrations/snyk-ci-cd-integrations/github-actions-for-snyk-setup-and-checking-for-vulnerabilities.md)
* [Jenkins integration](/developer-tools/integrations/snyk-ci-cd-integrations/jenkins-plugin-integration-with-snyk.md)
* [Maven integration](/developer-tools/integrations/snyk-ci-cd-integrations/github-actions-for-snyk-setup-and-checking-for-vulnerabilities/snyk-maven-action.md)
* [TeamCity integration](https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/teamcity-jetbrains-integration-using-the-snyk-security-plugin)
* [Terraform Cloud integration for IaC](/developer-tools/integrations/snyk-ci-cd-integrations/terraform-cloud-integration-for-snyk-iac-using-run-tasks/set-up-the-terraform-cloud-integration-for-iac.md)
* [Terraform Enterprise integration for IaC](/developer-tools/integrations/snyk-ci-cd-integrations/terraform-enterprise-integration-for-snyk-iac.md)

For integration with GitLab pipelines, see this [pipeline configuration](https://github.com/snyk-labs/snyk-cicd-integration-examples/blob/master/GitLabCICD/gitlab-npm.yml).

For additional examples of binary and npm integrations for CI/CD, see [GitHub CI/CD examples](https://github.com/snyk-labs/snyk-cicd-integration-examples).

## Support policy <a href="#support-policy" id="support-policy"></a>

Snyk supports the latest 12 months of CI/CD plugin versions, ensuring functionality and performance. Older versions are considered End-of-Support (EOS) and will not receive bug fixes or troubleshooting.

Snyk provides fixes only in new versions and cannot fix older versions. Customers must upgrade to benefit from improvements.

This policy fosters innovation while optimizing resources.

If you need help, submit a [request](https://support.snyk.io/) to Snyk Support.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations.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 `build a script that syncs our docs to a CMS` 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.