draft: promotion pipeline — build once, promote the artifact (RFC Flight half)#423
Closed
Omicron7 wants to merge 2 commits into
Closed
draft: promotion pipeline — build once, promote the artifact (RFC Flight half)#423Omicron7 wants to merge 2 commits into
Omicron7 wants to merge 2 commits into
Conversation
Implementation sketch for the Flight half of the Agentic Development Lifecycle RFC: env-neutral candidate builds, digest-based promotion of the reviewed stage image to production, release tags as rollback points, one-click rollback, and the shared production lock. Design doc in docs/promotion-pipeline.md covers naming, cru-deploy wrappers, required changes to the deploy actions (explicit image input), app-repo migration steps, and open questions (env-neutral BUILD secrets, release record of truth, re-tag IAM, stage build scheduling). Merge-gate/review-policy changes are out of scope - this machinery works with or without human PR review. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
deployment mark no longer exists in datadog-ci v5 (see PR #425); update the stubs to the pinned dora deployment pattern, with rollback recorded via a custom tag since dora has no --is-rollback. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #427 — the pipeline-v2 development branch implements this design for real (clean-break v2: new actions + workflows, no v1 modifications). The design doc evolved into docs/pipeline-v2.md on that branch; decision history lives in the design memo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implementation sketch for the Flight half of the Agentic Development Lifecycle RFC, opened as a draft to anchor the adoption discussion. Not for merge as-is — the deploy steps are TODO stubs; the value is the shape, naming, and open-questions list.
docs/promotion-pipeline.md— the design: image flow, tag naming (candidate-<n>/sha-<gitsha>/release-<r>), cru-deploy wrapper examples, required changes to the existing deploy actions, per-repo migration steps, and open questions.build-candidate.yml— env-neutral candidate build from tip ofmain(skeleton).promote.yml— resolves the digest actually running on stage and deploys that digest to production (race-free: what was reviewed is what ships), tags itrelease-<r>, marks the deployment in Datadog. Carries the shared productionconcurrencylock and binds theproductionGitHub Environment (the human gate).rollback.yml— redeploy a prior release digest,--is-rollbackmarked; the future execution target for severity-gated auto-rollback.Deliberately out of scope
Merge-gate / review-policy changes. This machinery works identically with or without human PR review — which is what lets it ship first, per the phased adoption plan.
Key open questions (details in the doc)
sharednamespace vs prod-bound)imageinput (bypass<env>-<build>construction)Relates to #421 / #422 (Datadog deploy telemetry — the observability side of the same phase).
🤖 Generated with Claude Code