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
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 a weird issue with a bamboo build I have setup. The first step is to checkout the latest revision in the trunk of our SVN repo.
Looking at the logs after the job completes, I see it checking out \trunk but then it lists the revision number as something like 667 (or the latest rev from a branch), when the latest revision committed to the trunk would be 655.
I can't find any reason as to why this is happening. Am I overlooking something obvious?
EDIT: I will also add that I have been running manual builds. Would this cause it to pull whatever is the latest rev? I have a repo polling action setup so I can wait until someone merges with the trunk to see what rev that build pulls.
See photos for the config of the repo (which is used by other projects without any of these issues) and the revision named in the build logs vs the actual latest branch revision.
Its a limitation in Bamboo. It only checkout the global repo revision.
Feature request https://jira.atlassian.com/browse/BAM-10396
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.