Bamboo checking out branch revision when it should be checking out trunk only

[Steven Miller]

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.

[Foong]

Its a limitation in Bamboo. It only checkout the global repo revision.

Feature request https://jira.atlassian.com/browse/BAM-10396