Absolutely we will try it out.
Thanks for over-delivering on the original checkout-only strategy!
I wasn't complaining but didnt want to spend time testing if it would not support the change detection.
Thanks again for continuing to support a great set of products!

Eric, I think it's best if you try the EAP to see if it suits your needs.
I know that at some point we promised less (just checkout), but we've delivered more

Solution available in 3.3 allows to:

• define multiple repositories per plan
• every repository defined for plan could be selected for change detection (so, you CAN use multiple repositories for triggering the build)
• there is only one strategy per plan - but this strategy applies to ALL repositories selected to be a part of change detection - for example if you select to poll 3 of 5 defined repositories to be queries every 3 minutes, 3 repositories would be queried (those selected for change detection)

Hope that explanation helps

Can you confirm that this fix does NOT provide for multiple repositories to be polled for changes but merely allows multiple repositories to be synced AFTER a change is detected via a single repository or some other mechanism? If so, this fix does not provide the functionality we need and we look forward to a complete solution. The "workarounds" do not work via Perforce because the relative layout of multiple workspace code trees to each other is not maintained when synced.

Bamboo 3.3 now supports multiple repositories. This should be available next week.

Please contact us through support if you have any issues with it.

Hi,
I've added 3.3.rc3 version to JIRA. So, got ahead with feedback.

Thanks

Hi Jens,

I've installed the 3.3-rc3 upgrade and I'm currently testing it out. Looks
good so far, however I spotted one minor issue. Where should I submit
feedback? I started filling out a JIRA issue but the Affects Version/s field
only contains released versions and won't allow v3.3-rc3. Thanks.

-Dan

On Fri, Sep 30, 2011 at 4:23 PM, Jens Schumacher [Atlassian] (JIRA) <

–
Dan DiCara
The Broad Institute of MIT and Harvard
301 Binney Street, Desk 5159-C
Cambridge, MA 02142
(617) 714-8281

I'm happy to announce that the Bamboo 3.3 EAP, featuring support for multiple repositories, is now available at:

http://www.atlassian.com/software/bamboo/BambooEAPDownloads.jspa

Please download it and give it a try. We would love to get some early feedback.

We are also very much interested in this feature. We have this currently in Teamcity and are considering slowly moving over to bamboo to also take advantage of some integration into Jira. The second repository for us is just to pull down build scripts. We use this approach to sometimes have agents on machines we deploy too and take advantage of the ability to pull down builds along with build scripts to handle deploys.

we would like to keep it lightweight and merely allow for checking out additional repositories.

At the very least, this solves my use case, where I have bamboo agents inside and outside our intranet. The ones outside should grab from the public repo at sourceforge, and the ones inside should grab from our private copy on the intranet to avoid having 10 agents all pulling the exact same thing over our internet connection. They're both the exact same code, just in different places.