As per the usual convention, branches aren't stored under /trunk, but under /branches instead, with /trunk/ being the main development line only. When a repo is configured to have a branch path inside /trunk, Bamboo doesn't recognize ' trunk' as being a branch folder (as per the usual Subversion convention), therefore, it tries to find a /branches folder inside /trunk.Then, when performing branch detection, it removes the /some_branch portion and searches under /branches. If a repository is defined in Bamboo with the branch path pointing to /branches/some_branch, Bamboo checks the branch path ( /branches/some_branch) and understands that path as where the branches reside.If the repository root URL is pointing to a branch already (instead of the repository), it won't find any /branch nor /branches folders within that branch, thus we'll see the errors in the logs.

Unless you specify the branch detection path manually, Bamboo will search for branches under the repository's root URL, at the /branch and /branches subfolders.Bamboo branch detection for Subversion repositories This comes from Bamboo trying to detect branches on SVN repositories that are misconfigured or follow a different structure than SVN's default one, so the paths Bamboo tries to detect branches on don't exist. Svn branch detected: svn+ssh:///branches/, but doesn't start with root svn+ssh:///trunk/ Cause

Snail svn