When triggering dependent builds, repository revisions for common repositories are not preserved

http://confluence.atlassian.com/display/BAMBOO/Setting+up+Build+Dependencies suggests that for dependent plans, revisions are preserved. With the advent of multiple repositories, it is not obvious that this is only the case only if the repository sets of both plans are the same, i.e. they need to have the same set of repositories, and the same credentials.

We were tripped up by this with dependent plans, but the dependent plan having an additional repository. Even though there were other common repositories, the revisions for these common repositories were not preserved. I would have expected the revisions for the common repositories to be preserved.

A workaround exists to have the same repository sets for the triggering plan and dependent plan, but it is not obvious and doesn't seem to be documented anywhere.