Using Docker Scout in Continuous Integration Pipelines

content/manuals/scout/integrations/ci/_index.md

78f0f215d3ac8d7eee4257d801b5bc7102c273794710bb2f000000030000036c

---
description: How to setup Docker Scout in continuous integration pipelines
keywords: scanning, vulnerabilities, Hub, supply chain, security, ci, continuous integration,
  github actions, gitlab
title: Using Docker Scout in continuous integration
linkTitle: Continuous Integration
aliases:
- /scout/ci/
---

You can analyze Docker images in continuous integration pipelines as you build
them using a GitHub action or the Docker Scout CLI plugin.

Available integrations:

- [GitHub Actions](gha.md)
- [GitLab](gitlab.md)
- [Microsoft Azure DevOps Pipelines](azure.md)
- [Circle CI](circle-ci.md)
- [Jenkins](jenkins.md)

You can also add runtime integration as part of your CI/CD pipeline, which lets
you assign an image to an environment, such as `production` or `staging`, when
you deploy it. For more information, see [Environment monitoring](../environment/_index.md).

Chunks

b2102252 (1st chunk of `content/manuals/scout/integrations/ci/_index.md`)

Title: Using Docker Scout in Continuous Integration Pipelines

Summary

This document describes how to integrate Docker Scout into continuous integration (CI) pipelines to analyze Docker images as they are built. It provides links to specific guides for GitHub Actions, GitLab, Microsoft Azure DevOps Pipelines, Circle CI, and Jenkins. It also mentions the possibility of adding runtime integration for environment monitoring.