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?
Unfortunately not. You have to follow one of the approaches you've outlined or create repositories using externals and check them out in Bamboo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.