BuildReleaseRun [principle] v1.0.0

The deployment pipeline has three strictly-separated stages. Build converts code to an executable bundle. Release combines a build with a config to produce an immutable, identifiable release. Run executes the release in the target environment. You cannot edit code on the running server, and once a release is created its config is frozen.

Build → Release → Run are three stages that flow one direction. No mutation in production.

Applies To

• Build artifact: a versioned container image, jar, or zip — never 'the current main branch'.
• Release: image + config snapshot, tagged with a unique release ID. Rollback = redeploy a prior release ID.
• Run: launch the release; do not SSH in to edit files.

BuildReleaseRun [principle] v1.0.0

The deployment pipeline has three strictly-separated stages. Build converts code to an executable bundle. Release combines a build with a config to produce an immutable, identifiable release. Run executes the release in the target environment. You cannot edit code on the running server, and once a release is created its config is frozen.

Build → Release → Run are three stages that flow one direction. No mutation in production.

Applies To

• Build artifact: a versioned container image, jar, or zip — never 'the current main branch'.
• Release: image + config snapshot, tagged with a unique release ID. Rollback = redeploy a prior release ID.
• Run: launch the release; do not SSH in to edit files.

Relations

requires: [@backend-architecture/principle-codebase-one-per-app]

Requires

• @backend-architecture/principle-codebase-one-per-app