I'm evaluating Bamboo as a replacement for our aging CruiseControl system. We build a number of different Eclipse-based products. Each Eclipse product is composed of many plugins, with a lot of overlap across products. We have several Subversion repositories; each repository contains many plugins: for example, trunk/ might contain 100 plugins at the top level in a given repository. To build a product, we pull a laundry list of different plugins from the various repositories, compile and assemble them. We have all this working in CruiseControl: the build script reads a list of repositories and plugins and invokes the CruiseControl Subversion tasks as appropriate, either as part of a change monitor or for the actual checkout/build. How can we do something similar in Bamboo? The two alternatives I see are to create a separate repository for each plugin (ugh) or use some sort of bootstrap script which circumvents Bamboo's machinery and does the checkouts directly (ugh again.) Is there a better alternative for this kind of fine-grained checkout in Bamboo?
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs