Menu

Our order service built against a library snapshot someone had deployed from a feature branch
📰

Our order service built against a library snapshot someone had deployed from a feature branch

DEV Community: cicd·Sergey Shinder·about 5 hours ago
#DXzUL2rO
#devtocicd#devto#dev#branch#snapshot
Reading 0:00
15s threshold

Our pricing rules live in a shared Java library that four services depend on. Between releases its main branch publishes 2.3.0-SNAPSHOT to our Nexus repository, and the services' main branches depend on that snapshot so they pick up rule changes without waiting for a release. That arrangement had worked for three years.

In October an engineer working on a branch that changed how pallet surcharges round ran mvn deploy from his laptop, to try the change in a test environment. It published as 2.3.0-SNAPSHOT, because that is what the branch's pom said. Nexus accepted it, as it accepts every snapshot deploy from anyone with write access.

A snapshot version is not a build. It is a name for whichever timestamped build was deployed last. Maven resolves it by reading the version's maven-metadata.xml in the remote repository and taking the newest entry, and nothing in that file records which branch a build came from.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.