Promote an artifact from staging to release without rebuilding it
Tests immutable artifact discipline. Answer: promote by copying the binary or retagging the image digest, never recompiling, because rebuilds introduce dependency drift and untested bits.
Tests fluency with immutable artifacts and the principle that the same binary must flow through every environment. A strong answer describes a promotion process such as copying a JAR between repository managers or retagging a Docker image digest in a registry, keeping the artifact bit-for-bit identical. It then explains that rebuilds risk non-deterministic dependencies, toolchain variance, and shipping code that never passed staging.
Read the original → beyond.minimumcd.org
- #ci/cd
- #immutable-artifacts
- #devops
- #deployment-pipeline
- #release-engineering
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.