Bitbucket Pipelines

Overview

This document shows how to use the CodeAnt Quality Gates pipe in your Bitbucket pipelines. Reference Repository: quality-gates-codeant

Setup

1. Create a CodeAnt Token

In CodeAnt AI, open the user menu (click your email at the bottom-left) and select API Tokens, click Create token, and copy the generated token (it starts with cdt_ and is shown only once). See API Tokens for the full walkthrough. This single token authenticates the scan - you don’t need a Bitbucket access token or app password.

2. Configure Repository Variables

Before using the pipe, configure this repository variable in Repository Settings → Pipelines → Repository variables:

CODEANT_TOKEN - Your CodeAnt token (cdt_…)

Note: In the examples below the pipe expects a pipeline variable named ACCESS_TOKEN which is set from the repository variable; e.g. ACCESS_TOKEN: $CODEANT_TOKEN. This mapping is required so the container receives the token at runtime.

Basic Usage

Example 1: Run Quality Gates on Every Push

image: atlassian/default-image:3

pipelines:
  default:
    - step:
        name: CodeAnt Quality Gate Scan
        script:
          - pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
            variables:
              ACCESS_TOKEN: $CODEANT_TOKEN

Example 2: Run Quality Gates on Pull Requests Only

image: atlassian/default-image:3

pipelines:
  pull-requests:
    '**':
      - step:
          name: CodeAnt Quality Gate Scan
          script:
            - pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
              variables:
                ACCESS_TOKEN: $CODEANT_TOKEN
                API_BASE: "https://api.codeant.ai"
                TIMEOUT: "300"
                POLL_INTERVAL: "15"

Example 3: Run Quality Gates with Custom Configuration

image: atlassian/default-image:3

pipelines:
  branches:
    main:
      - step:
          name: Build Application
          script:
            - echo "Building application..."
            - npm install
            - npm run build

      - step:
          name: CodeAnt Quality Gate Scan
          script:
            - pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
              variables:
                ACCESS_TOKEN: $CODEANT_TOKEN
                API_BASE: "https://api.codeant.ai"
                TIMEOUT: "600"
                POLL_INTERVAL: "20"

Example 4: Multi-Stage Pipeline with Quality Gates

image: atlassian/default-image:3

pipelines:
  branches:
    main:
      - parallel:
          - step:
              name: Run Tests
              script:
                - npm install
                - npm test

          - step:
              name: CodeAnt Quality Gate Scan
              script:
                - pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
                  variables:
                    ACCESS_TOKEN: $CODEANT_TOKEN

      - step:
          name: Deploy to Production
          deployment: production
          script:
            - echo "Deploying to production..."
            - ./deploy.sh

Example 5: Quality Gates with Debug Mode

image: atlassian/default-image:3

pipelines:
  custom:
    debug-scan:
      - step:
          name: CodeAnt Quality Gate Scan (Debug)
          script:
            - pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
              variables:
                ACCESS_TOKEN: $CODEANT_TOKEN
                API_BASE: "https://api.codeant.ai"
                DEBUG: "true"

Configuration Variables

Variable	Required	Default	Description
`CODEANT_TOKEN`	Yes	-	CodeAnt API token (`cdt_…`) for authentication - see API Tokens (set as repository variable and pass as `ACCESS_TOKEN: $CODEANT_TOKEN` in pipeline)
`API_BASE`	No	`https://api.codeant.ai`	Base URL for CodeAnt API
`TIMEOUT`	No	`300`	Maximum time in seconds to wait for results
`POLL_INTERVAL`	No	`15`	Time in seconds between polling attempts
`DEBUG`	No	`false`	Enable debug mode for verbose logging

How It Works

The pipe fetches the quality gates script from the CodeAnt API
It initiates a quality gate scan for your repository and commit
It polls for results until the scan completes or times out
If secrets or issues are detected, the pipeline fails
If the quality gate passes, the pipeline continues

Execution Time Considerations

⏱️ Performance Options:

Default behavior (with result waiting): ~5-7 minutes
- Triggers scan and waits for complete analysis results
- Provides immediate feedback on secrets and security issues
- Best for comprehensive CI/CD pipelines where you need instant validation
Custom timeout settings: Adjust based on repository size
- Use TIMEOUT: "600" (10 minutes) for larger repositories
- Use POLL_INTERVAL: "20" to reduce API polling frequency
- Results can also be viewed in the CodeAnt dashboard

Tip: For faster PR checks on larger repositories, increase the timeout to avoid premature pipeline failures while the scan completes.

Quality Gate Checks

The quality gate performs comprehensive checks including:

Security and Code Quality Checks

Secret Detection: Scans for hardcoded secrets, API keys, passwords, and tokens
SAST (Static Application Security Testing): Detects security vulnerabilities in source code
SCA (Software Composition Analysis): Identifies vulnerabilities in third-party dependencies
IaC (Infrastructure as Code): Scans infrastructure configuration files for security issues
Duplicate Code Detection: Identifies code duplication to improve maintainability
Analyzes only the changed lines since your merge base commit
Uses high-confidence detection to minimize false positives
Blocks the build if any issues are found

Troubleshooting

Pipeline Fails Immediately

Issue: Pipeline fails with “ACCESS_TOKEN is required but not set” Solution: Ensure you’ve set CODEANT_TOKEN in your repository variables.

Pipeline Times Out

Issue: Pipeline times out waiting for results Solution: Increase the TIMEOUT variable:

- pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
  variables:
    ACCESS_TOKEN: $CODEANT_TOKEN
    TIMEOUT: "600"  # 10 minutes

Connection Issues

Issue: Cannot connect to CodeAnt API Solution: Verify the API_BASE URL and check if you need to use a custom endpoint:

- pipe: docker://public.ecr.aws/d2p9q4a9/quality-gates:latest
  variables:
    ACCESS_TOKEN: $CODEANT_TOKEN
    API_BASE: "https://api.codeant.ai"

Support

📧 Email: support@codeant.ai
📚 Documentation: https://docs.codeant.ai
🐛 Repository: https://bitbucket.org/codeantworkspace/quality-gates-codeant/src/main/

License

MIT License - see LICENSE file for details## Token permission This pipeline authenticates with a CodeAnt API token (cdt_…). If the token is scoped, give it the Codeant CI/CD role - it covers scans, quality gates, and test-coverage upload - scoped to the repositories this pipeline runs on (or All repositories). A token missing the required permission is rejected with an HTTP 403 token_scope_forbidden error that names the permission it needs. See API token permissions.

Get Started

AI Code Review

Scan Center

Code Security

Cloud Security

Code Quality

Engineering Metrics

IDE

CLI

CI/CD

Integrations

Rule Reference

How CodeAnt Uses CodeAnt

Resources

Overview

Setup

1. Create a CodeAnt Token

2. Configure Repository Variables

Basic Usage

Example 1: Run Quality Gates on Every Push

Example 2: Run Quality Gates on Pull Requests Only

Example 3: Run Quality Gates with Custom Configuration

Example 4: Multi-Stage Pipeline with Quality Gates

Example 5: Quality Gates with Debug Mode

Configuration Variables

How It Works

Execution Time Considerations

Quality Gate Checks

Security and Code Quality Checks

Troubleshooting

Pipeline Fails Immediately

Pipeline Times Out

Connection Issues

Support

License

​Overview

​Setup

​1. Create a CodeAnt Token

​2. Configure Repository Variables

​Basic Usage

​Example 1: Run Quality Gates on Every Push

​Example 2: Run Quality Gates on Pull Requests Only

​Example 3: Run Quality Gates with Custom Configuration

​Example 4: Multi-Stage Pipeline with Quality Gates

​Example 5: Quality Gates with Debug Mode

​Configuration Variables

​How It Works

​Execution Time Considerations

​Quality Gate Checks

​Security and Code Quality Checks

​Troubleshooting

​Pipeline Fails Immediately

​Pipeline Times Out

​Connection Issues

​Support

​License

Overview

Setup

1. Create a CodeAnt Token

2. Configure Repository Variables

Basic Usage

Example 1: Run Quality Gates on Every Push

Example 2: Run Quality Gates on Pull Requests Only

Example 3: Run Quality Gates with Custom Configuration

Example 4: Multi-Stage Pipeline with Quality Gates

Example 5: Quality Gates with Debug Mode

Configuration Variables

How It Works

Execution Time Considerations

Quality Gate Checks

Security and Code Quality Checks

Troubleshooting

Pipeline Fails Immediately

Pipeline Times Out

Connection Issues

Support

License