Commercial CI/CD
CI/CD control for teams shipping paid software
Use self-hosted runners and the implemented hosted Linux execution path with four source providers, protected deployments, release evidence, and billing controls. Hosted production use remains subject to access approval and launch-hardware validation.
Hosted Linux execution
Platform images, per-job containers, optional rootless Docker sidecars, source checkout, and conventional output collection are implemented. Hosted logs are attached after execution rather than streamed, full scoped-secret parity is incomplete, and production hardware must pass launch canaries.
Four source providers
GitHub, GitLab, Bitbucket, and Azure Repos have connection, repository sync, webhook-triggered run, checkout credential, and status-publishing code paths. Changed-file retrieval, replay behavior, OAuth lifecycle, and live compatibility vary by provider and require launch evidence.
Release control
Protected environments, approvals, deployment records, target plans/results, rollback records, notifications, audits, and generated compliance files are implemented. Deployment work requires configured active targets and self-hosted runner tooling.
Workflow map
Source: connect provider apps or Shipline Git, then sync repositories.
Build: choose hosted Linux or self-hosted runners and collect release outputs from conventional directories.
Promote: approve protected environments, execute target commands on self-hosted capacity, and generate compliance records.
Implementation status
The control plane schedules dependencies, reconciles hosted terminal work, restores declared trusted caches, and reconciles closed-period overages. Real-worker, payment-lifecycle, and production evidence remain required.