A release pipeline builds separately for staging and production using floating dependency versions. Staging tests pass, but production behaves differently. Which changes best connect test evidence to the deployed release? Select 2 answers.

Published
  1. Build one identified artifact and promote that same content through the release stages.
  2. Treat the artifact filename as proof of identical content across every build.
  3. Record source revision, dependency versions, artifact digest, and environment configuration for release traceability.
  4. Rebuild from whichever branch is newest at every deployment stage.
  5. Disable staging tests so the inconsistency is no longer visible.

Comments — 0