Skip to content

GitLab CI Integration

Quick Start

Add the following configuration to your .gitlab-ci.yml:

Escape:
  stage: post-deploy
  needs:
    - deploy # name of your deployment job
  variables: # you can find those secrets directly in your Escape Application Settings
    - ESCAPE_APPLICATION_ID: $ESCAPE_APPLICATION_ID
    - ESCAPE_API_KEY: $ESCAPE_API_KEY
  image: node:alpine
  before_script:
    - npm install -g @escape.tech/action
    - npm show @escape.tech/action version
  script:
    - escape-action
  allow_failure: true
  only:
    refs:
      - staging

Configuration Options

Environment Variables

  • ESCAPE_APPLICATION_ID: Your Escape application identifier
  • ESCAPE_API_KEY: Your Escape API key

Pipeline Settings

  • stage: Recommended to run after deployment
  • allow_failure: Set to true for non-blocking scans
  • only/refs: Specify branches for scan execution

Failure behavior

The Escape CLI will:

  • Exit with code 1 if high-severity issues are found
  • Can be configured to fail on different severity levels

Available variables and options

See CLI documentation for complete configuration options.