Hi Team,
Is there any use case or an example of handling multiple projects with multiple plans and a deployment strategy for Bamboo Specs. I have gone through the docs and example for specs. But it does not give the visibility or approach to understand how Atlassian expects the Bamboo Projects and Plan (Multiple) to handled using specs. It would be great to have an example for customers so that they are in proper standard path in their future strategy.
Regards,
Bru
Every team is unique and use Bamboo in any possible way. I can say about Bamboo dev team approach.
We have separate repository which holds all our plans/deployments in Java code. There're utility classes to hold generic tasks like Maven, test parsers, Docker etc. And then we have main entry class
@BambooSpecpublic class PlanUploader {@NotNull public static Project defaultProject() {return Projects.mainProject(); }@NotNull private static List<BambooPlan> getPlans() {return Arrays.asList(// A plans new CoreBuildsPlan(), ... ); }@NotNull private static List<BambooDeployment> getDeployments() {return Arrays.asList( ...new BambooReleaseDeployment() ); }public static void main(String[] args) {publishAll(Servers.bambooTeamServer(), getPlans(), getDeployments()); }private static void publishAll(@NotNull BambooServer bambooServer, @NotNull List<BambooPlan> plans, @NotNull List<BambooDeployment> deployments) {final List<RootEntityPropertiesBuilder<?>> entities = new ArrayList<>();plans.forEach(bambooPlan -> entities.add(bambooPlan.getPlan()));deployments.forEach(bambooDeployment -> {entities.add(bambooDeployment.getDeployment());entities.addAll(bambooDeployment.getEnvironmentPermissions()); });entities.forEach(entity -> publish(bambooServer, entity)); }private static void publish(@NotNull BambooServer bambooServer, @NotNull RootEntityPropertiesBuilder builder) { System.out.println(bambooServer.publish(builder)); }}
It looks like you're new here. Sign in or register to get started.