Opscraft
Build tools & artifact repositories · Lesson 1 of 9 · 3 min read

Why build tools and artifact management matter

Build tools and artifact repositories sit between source code and the container image. Senior DevOps interviews ask how Maven and Gradle actually resolve and build, why builds are slow or non-reproducible, how versions and SNAPSHOTs work, how Nexus/Artifactory/CodeArtifact proxy and host artifacts, and how you'd design an artifact flow that is fast, auditable and secure. This topic also covers the other ecosystems you'll meet (npm, pip, Go) at the level a platform engineer needs.

The flow from commit to deployable

Enlarge diagramSourcea commit in GitBuild toolMaven or Gradle: compile, test,packageArtifactorders-1.4.0.jarArtifact repositoryNexus, Artifactory, CodeArtifactContainer imagecopies the artifact, pushed toECRClusterruns the image by digest123456
Figure 1. From commit to running service. The build tool makes an artifact once; every later step reuses that exact artifact.
Swipe sideways to see all of it, or tap to open it full screen.

What a platform engineer owns here:

  • Reproducibility — the same commit produces the same artifact; dependencies are pinned and resolved from a controlled source.
  • Speed — caching of dependencies and build outputs; incremental and parallel builds.
  • Traceability — every artifact maps to a commit, a build and its dependency list (SBOM).
  • Security — dependencies come through a proxy you control, are scanned, and credentials to publish are least-privilege.
  • Immutability — a released version is never overwritten.

Build once, promote everywhere

Build the artifact once, give it an immutable version, and promote that exact binary (or image digest) through dev → staging → prod. Rebuilding per environment risks different dependency resolution, different compilers, and "it worked in staging". Environment differences belong in configuration, not in the binary.

Enlarge diagramCI buildone image, onedigestdevsame digeststagingsame digestprodsame digest
Figure 2. Build once, promote everywhere: the same binary moves through every environment. Rebuilding per environment means prod runs something nobody tested.
Swipe sideways to see all of it, or tap to open it full screen.