Commercial CI/CD
Launch documentation
Connect a provider, sync repositories, choose hosted or self-hosted runners, define pipelines, publish artifacts, and deploy with approvals.
1. Connect source
Install the GitHub App or connect GitLab, Bitbucket, and Azure Repos with OAuth/provider-app credentials or documented fallback tokens.
2. Define pipelines
Use YAML triggers, stages, jobs, dependency scheduling, bounded matrices, protected-environment approvals, built-in tasks, scoped secret snapshots, declared caches, publish staging, and same-run artifact download. Read the Pipeline YAML reference for supported runtime behavior and remaining limits.
3. Collect evidence
Collect bounded logs, artifacts, tests, coverage, cache-archive metadata, approvals, deployment records, rollbacks, and generated compliance files. Logs are persisted in the relational repository; output files use the artifact store. Review the execution documentation for hosted reconciliation limits.
Launch operator path
Prepare: connect source, create or import repositories, define YAML, configure runners, and save scoped secrets.
Prove: run pipelines, review artifacts/tests/coverage/caches/source checks, and approve protected deployments.
Operate: monitor status, support diagnostics, billing controls, webhooks, cleanup, and exports.
Evidence handoff links
Hosted runners · Source providers · Billing · Agent Tasks · Troubleshooting