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
This my scenario:
I provide a service which is composed by 7 apps. Each one of these apps is stored in one Git repository. When I develop a new feature for my "service" it means that I have to create a develop branch in each repository.
As Bamboo is designed, I had to create 7 Build plans. When I create a new feature, one "develop" branch is created in each repository and, also, its corresponding plan branch in each bamboo build plan. So far so good.
The problem comes in Bamboo when deployment environments are involved. I want to select a TEST environment for this new set of branches. As bamboo is designed, I have to go by each of the Deployment project one by one and
this is too tedious for me, so my question (and conclusion of this) is:
Am I missing something/some other way of achieving this (this = a better or more automatic way of assigning the same deployment environment for a set of deployment projects)?
You're not missing anything, this is the standard process to follow if you want to deploy results from a specific branch.
If you're running one of the latest Bamboo versions, it might be a good idea start thinking on managing your plans/deployments using Bamboo Java Specs, this will allow you to manage not only this but all other aspects from your CI/CD workflow.