You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have a Delphi program that is then customised for each customer. How can Bamboo structure be organized to build multiple projects concurrently and the ability to run each one if necessary?
All the code is in branch default of a single repository.
If they are put into jobs then if one fails all the plan will fail, is there another approach to organize the building process? ie get code from repository, build each single project for each customer and then move the generated files into deployment directory
Any help would be appreciated.
This seems to be a perfect use case for Bamboo Specs, which allow you to specify your configuration as code (and optionally manage it as repository-stored Bamboo Specs), either in Java, or for a subset of Bamboo features also in YAML - please refer to the Bamboo Specs Reference for examples of both approaches.
You could define your plan once and then iterate of the list of customers to generate a completely isolated Bamboo plan or even project per customer, possible accounting for subtle differences via conditional logic in the Bamboo Specs. Once your configuration changes, those changes will be applied to all plans/projects automatically.
Please refer to Tutorial: Create a simple plan with Bamboo Java Specs for an walk through with Java.