You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have written a library to encapsulate a bunch of common spec details for my colleagues to use to spec their plans concisely.
Let's say that I release mylib-5.6.7-SNAPSHOT and it's the first of that version. My specs scan ok, including that maven downloads the snapshot. If I release a subsequent mylib-5.6.7-snapshot (via maven unique naming convention of course!), it seems to me that the maven in Bamboo server is not refreshing the new snapshot version.
Jobs running on agents doing "mvn clean test" work just fine. They download the latest snapshot and run without a hitch. Only when I get to the server and scan via linked repo feature only then does the "download the newer maven-unique-named version of the snapshot" seem to not happen.
Anybody ever see that?