Certyn CI/CD integration is CLI-first.

On GitHub, use certyn/action@v1 or direct CLI steps.
On other CI systems, use direct CLI commands.

Certyn does not require branch strategy changes. Place checks at your existing decision points.

How it works

Run verification

Trigger a process with certyn run <process> --project <slug> --environment <key>.

Wait and gate

certyn run waits for terminal state by default and exits non-zero when the quality gate fails.

Consume outputs and artifacts

Use CLI JSON output or GitHub outputs to surface run_id, status links, and pass/fail counts.

Recommended setup

1) Use two suites: smoke and regression

Smoke Suite: smoke-suite for fast critical-path checks
Regression Suite: regression-suite for 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.

See: Scheduling & Automation

After a failed gate: triage flow

Use CLI triage commands to move from failed gate to root cause quickly:

certyn issues list --project my-app --activity attention
certyn executions for-issue --project my-app <issue-id>
certyn tests report --project my-app <testcase-id>

See full workflow: CLI Triage Workflows

For operator follow-up actions (issue updates, testcase updates, execution retry/stop), see: