CI/CD Pipeline Tools
Automating build, test, and deployment on every code change.
No build or CI pipeline exists in Decentralized.Host. You build artifacts elsewhere, push them with `dh artifact push` (or reference a digest-pinned image) and apply a manifest; any CI system can run those commands.
CI vs. CD, concretely
Continuous Integration (CI) means every code change is automatically built and tested before it's trusted -- catching breakage the moment it's introduced rather than at release time. Continuous Deployment/Delivery (CD) means a change that passes CI is automatically pushed toward production (deployment) or made ready to release with one click (delivery). GitHub Actions, GitLab CI, Jenkins, and Buildkite are common engines for the CI half; how the CD half looks varies enormously by team.
Automating build, test, and deployment on every code change. No build or CI pipeline exists in Decentralized.Host. You build artifacts elsewhere, push them with `dh artifact push` (or reference a digest-pinned image) and apply a manifest; any CI system can run those commands.