CI/CD Integration
Trigger Certyn runs from pipelines, ask Certyn for release review, and gate deploys.
Certyn CI/CD integration is designed for pipeline gates and release automation.
- On GitHub, use
certyn-one/action@v1. - On GitLab CI, Jenkins, CircleCI, Azure DevOps, Bitbucket Pipelines, and other systems, use the CI Runs API.
Certyn does not require branch strategy changes. Place checks at your existing decision points.
How it works
Run verification
Trigger a process with certyn-one/action@v1 or POST /api/ci/runs.
Wait and gate
Wait for a terminal state and fail the pipeline when failed > 0 or blocked > 0.
Consume outputs and artifacts
Use GitHub Action outputs or CI Runs API status fields to surface run links and pass/fail counts.
Recommended setup
1) Use two suites: smoke and regression
- Smoke Suite:
smoke-suitefor fast critical-path checks - Regression Suite:
regression-suitefor broad nightly coverage
Use process slugs and aliases (smoke, regression) so suite composition stays configurable in Certyn.
2) Keep strict gates at decision points
| Decision point | What to run | Gate rule |
|---|---|---|
| Pull request merge | smoke | fail if failed > 0 or blocked > 0 |
| Deploy/promotion | smoke | fail if failed > 0 or blocked > 0 |
| Nightly quality sweep | regression | fail run and alert owners |
3) Keep deploy traceability with environment version
After deploy, update environment version (commit SHA, image tag, or release version) for auditability and trigger tracking.
Authentication
Create an API key from Settings -> API Keys.
Recommended CI scopes:
ci:triggerci:statusci:cancel
Guides
GitHub Actions
Use certyn-one/action@v1 for PR gates, deploy gates, release review, and Ask Certyn workflows.
GitLab and Other CI
API-based integration patterns for GitLab CI, Jenkins, CircleCI, Azure DevOps, Bitbucket Pipelines, and generic shell runners.
CI Runs API
Low-level HTTP reference for systems that need raw API control.