This website uses cookies to ensure you get the best experience.
Learn more.
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
- Build one identified artifact and promote that same content through the release stages.
- Treat the artifact filename as proof of identical content across every build.
- Record source revision, dependency versions, artifact digest, and environment configuration for release traceability.
- Rebuild from whichever branch is newest at every deployment stage.
- Disable staging tests so the inconsistency is no longer visible.
Comments — 0
Sign in to comment