CI/CD
Раздел про CI/CD для backend-команды: принципы конвейера доставки, CI для Java/Spring с quality gates, стратегии релиза (rolling, blue-green, canary, флаги), trunk-based.
Why it matters for UCP. The delivery pipeline is what turns a methodology into pace: small vertical slices reach production daily only when the path from commit to release is boring and automatic. The pipeline's quality gates are where an executable standard becomes enforced. Part of the training program.
The section is split into four articles: principles, CI for our stack, release strategies, and how to organize branches and versions.
Articles in this section
- Pipeline principles — build the artifact once, fast before slow, pipeline as code, a green main, deploy ≠ release.
- CI for Java/Spring — stages, Gradle caches, Testcontainers in the pipeline, quality gates from the security guide.
- Release strategies — rolling, blue-green, canary with metrics, feature flags; the criteria for choosing.
- Branches and the release cycle — trunk-based, PR discipline, versioning, the GitOps loop.
Related
- Deploying to Kubernetes — where the pipeline delivers: manifests, rolling, GitOps.
- Security Style Guide — SAST/deps/secrets gates with rule codes.
- Test Strategy Style Guide — the test layers the pipeline runs.
- The executable engineering standard — the standards the gates make enforced.