advancedCI/CD with Docker: Jenkins, GitHub Actions & GitLab CI

Why is tagging images with 'latest' discouraged in CI/CD pipelines?

'latest' is a floating, mutable pointer — it doesn't tell you which specific commit or build produced the image currently running in any environment, making rollbacks, audits, and incident investigation far harder. Production pipelines should tag images by an immutable identifier like the git commit SHA or a monotonically increasing build number, so every deployed artifact traces back unambiguously to its source.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

Why is tagging images with 'latest' discouraged in CI/CD pipelines?

Next Step

Continue to What are Kaniko and Buildah, and why would you use them instead of standard docker build in CI?← Back to all Docker questions