Question

A development team uses a trunk-based workflow in a CodeCommit repository. Their CodePipeline builds a Java application with CodeBuild and publishes the resulting JAR to CodeArtifact. Currently every merge to main publishes a package with version 1.0.0-SNAPSHOT, which overwrites the previous artifact. QA reports that they cannot reliably reproduce a bug because the artifact tested last week no longer exists in the repository. The team wants each build to publish an immutable, uniquely versioned artifact that can be traced back to the exact source commit, without manual version edits. Which approach best meets this requirement?

Accepted Answer

In the buildspec, derive a unique version string (for example, a base version plus the CODEBUILD_RESOLVED_SOURCE_VERSION commit hash and build number) and publish that as the CodeArtifact package version so each build creates an immutable, traceable artifact.

Answer

Enable versioning on the CodeArtifact domain and keep publishing 1.0.0-SNAPSHOT so CodeArtifact automatically retains each historical copy of the package.

Answer

Add a manual approval action before the publish stage so a QA engineer manually increments the version in the pom.xml before each build is promoted.

Answer

Configure a CodePipeline S3 source bucket with versioning enabled and publish the JAR directly to S3 instead of CodeArtifact.