CI/CD Pipeline Integrations
First-party GitHub Action, Jenkins plugin and Azure DevOps task, plus a REST API for any other CI/CD tool.
What It Does
CI/CD Pipeline Integrations let you run your API test suites as part of every build, merge request or deployment. Results feed back into your pipeline so broken APIs are caught before they reach production. You can configure pass-rate thresholds (for example, fail the build only if the pass rate drops below 95%), choose whether errors fail the build, and decide whether a missed gate fails or only warns. Each integration writes JUnit XML and a JSON summary into the workspace, so your CI's own test tab shows the details, and the gate decision is available to later steps. The environment is set on the pack, so a branch that should test staging simply runs the staging pack. With a self-hosted installation, CI runs reach private APIs inside your network. Pipelines authenticate with scoped, rotatable API keys rather than a person's login.
Overview
Trigger API tests from GitHub Actions, Jenkins or Azure DevOps using first-party pre-built integrations. For GitLab CI, CircleCI, Bitbucket Pipelines, or anything else (Bamboo, TeamCity, Buildkite), use the public REST API with the same quality gate, so your pipeline fails only when it should. Map branches to packs that target dev, staging or production: the pipeline check fails or passes on the PR, and JUnit results show in your CI's test tab. A run already in progress is refused, so a pack never runs twice at once, and CI logins and CI-triggered runs are recorded in the audit log.
Key Capabilities
How It Works
- 1
Add the first-party integration (GitHub Actions, Jenkins, Azure DevOps) or call the REST API directly from any other CI/CD tool
- 2
Choose which test pack to run and the pass threshold; the pack sets the environment
- 3
Tests execute automatically on every push, PR or scheduled trigger
- 4
Pipeline fails if test thresholds are not met, with detailed reports and logs
- 5
View execution summaries and failure details in your CI/CD dashboard
Available on
professional Plan & Above
Upgrade to the professional plan to unlock this feature.
Documentation
Step-by-step guides for setting up and using CI/CD.
- Public APISettings > Integrations > Public API: Swagger and base URL, enable API, rate limits, token expiry, and which roles may use the API for CI/CD.
- CI/CD: Run Test Packs from GitHub ActionsRun a Shift-Left API test pack in a GitHub Actions workflow with the first-party action, gate the build on its pass rate, and publish the JUnit results.
- CI/CD: Run Test Packs from Azure DevOps PipelinesInstall the Shift-Left API extension from the Visual Studio Marketplace, add the task to an Azure Pipelines YAML file, gate the build on the pass rate, and publish the JUnit results.
- CI/CD: Run Test Packs from JenkinsInstall the Shift-Left API Jenkins plugin from its .hpi file, add the Run Test Pack build step to a Freestyle job, gate the build on the pass rate, and publish the JUnit results.
- CI/CD: Any CI via the REST API (GitLab, CircleCI, Bitbucket and others)Run a Shift-Left API test pack from GitLab CI, CircleCI, Bitbucket Pipelines, TeamCity or any CI that can run curl: sign in, start the pack, wait for the new run, and fail the job below your pass rate.
Go deeper
Guides and playbooks that show this capability in practice.