So I'm trying to figure out how to use Bamboo for CICD in a microservice environment. In our case, we have changes that go out as they pass each stage. One by one they just make their way into production. In other scenarios things have to go out in groups. For example, a scheduled release (because we need to train people before a launch date) or a fix that requires updates to multiple components that must be released together.
Right now, the system in place with Bamboo allows us to manually promote a build from one environment to another, no problem, but ideally what I want to be able to do is cut a release from Jira and then have bamboo pick up that trigger and search for all builds in deployment projects that are currently in an environment named 'staging' which also have the same release associated with them (through linked issues) and then automatically promote them to production. Of course, I'd need the ability to do roll them all back the same way. This is important because with large scheduled releases, it is possible that we'd be dealing with dozens of components and managing them all individually is going to be a real pain.
At first glance, it doesn't appear that Bamboo can support this and that it might be large enough to be out of scope of Bamboo in its current state. I'm looking for input or suggestions on how to manage this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.