Skip to main content
Automate security scanning by integrating Vidoc into your CI/CD pipelines.

CI Command

Use the dedicated ci command for automated environments:
The ci command runs in non-interactive mode, optimized for CI/CD pipelines.

CI Command Options

GitHub Actions

Store the Secret

  1. Go to GitHub repo → Settings → Secrets → Actions
  2. Click “New repository secret”
  3. Name: VIDOC_TOKEN
  4. Value: Your token from Vidoc dashboard

GitLab CI

Store the Variable

  1. Go to GitLab project → Settings → CI/CD → Variables
  2. Add variable: VIDOC_TOKEN
  3. Mark as “Masked” and “Protected”

CircleCI

Jenkins

Azure DevOps

Bitbucket Pipelines

Single-Tenant Installations

For self-hosted Vidoc, include the API URL:

Best Practices

Cache CLI Installation

Speed up pipelines by caching:

Use Profiles for Different Environments

Viewing Results

After CI scans complete:
  1. Go to app.vidocsecurity.com
  2. Select your project
  3. View issues in the dashboard
  4. Check PR-specific results in Pull Requests

Troubleshooting

”Unauthorized” in CI

  1. Verify VIDOC_TOKEN secret is set correctly
  2. Check the token hasn’t been revoked
  3. Ensure the token has proper permissions

Scan Timeout

For large codebases, increase your CI job timeout. First scans take longer due to initial indexing.

”No files found”

Ensure the checkout step runs before the scan and the working directory is correct.

CLI Scanning

Scan command details

Authentication

Token setup

API Keys

Manage tokens

Issues

Review results