Skip to main content

Azure pipelines

Prelude#

GitGuardian CI/CD integration with Azure Pipelines is performed through our CLI application ggshield. ggshield is a wrapper around the GitGuardian API for secrets detection, an API key is required for authentication.

⚠ Azure Pipelines does not support commit ranges outside of GitHub Pull Requests, therefore on push events in a regular branch only your latest commit will be scanned. This limitation doesn't apply to GitHub Pull Requests where all the commits in the pull request will be scanned.

Preview#

Azure Pipelines output

Installation#

Service accounts are recommended to run this integration.

Please note that service accounts are only available for workspaces under our Business plan, and their administration is restricted to Managers. If your workspace is under the Free plan, you can still use a personal access token to run this integration.

  1. Create a service account from the API section of your GitGuardian workspace (or a personal access token if you are on the Free plan).

  2. Add this API key to the gitguardianApiKey secret variable in your pipeline settings.

  3. Add a new job using ggshield to your Azure pipeline

jobs:- job: GitGuardianShield  pool:    vmImage: 'ubuntu-latest'  container: gitguardian/ggshield:latest  steps:  - script: ggshield scan ci    env:      GITGUARDIAN_API_KEY: $(gitguardianApiKey)