We a have a special "Release Build Plan" that produces the artifacts and tags the release in the VCS. This is a manually invoked plan as it requires a release identifier as custom input.
However, this plan still doesn't create a Release in Bamboo instead we still have to go in and manually create a Release that associates the outputs (artifacts) of that build with a Release.
Can this be automated in some fashion, prefereably as the last task of our "Release Build Plan"?
I thought so - but I am not sure that matches our needs. Our release name is set as part of the Release Build Plan as it goes into the VCS tag, as well as certain manifest files are updated based on it which then embeds it into the artifacts (jar files) generated and so on. So it has to "somehow flow" from the Release Build Plan into the trigger for the dummy deployment build. Is there a way of doing that, e.g. can the Release Build Plan set a global variable that we can then reference in the Deployment Project Release naming configuration?
Thanks for listening.
> This is a manually invoked plan as it requires a release identifier as custom input.
Reading this I was under impression that you use "Run customised..." and define release name as a variable there. If that's the case then it should work 'out of the box', just use the same variable name for Release name in Deployment Project.
All the variables' values (including manually defined ones) are saved & passed to the Deployment when you create a new release from a build result.
ATM The solution to this is hacky but possible. You can do this in the following way:
- In your Deployment Project create a dummy environement. Remove the default task (you won't need them) and add a simple Script Task that does nothing (exit 0 will do)
- Configure After Successful Plan trigger in your dummy Environment.
If you do this, every time the Release Build Plan ends sucessfully (including all the manual stages if you have those), the trigger will pick up the build result, create a release and launch the dummy environment.
I'm automatically creating releases on successful branch builds, as well as on the default branch. The deployment project that initiates the auto-release needs multiple triggers to handle this. I have had to manually define this trigger after the branch is created, though - so it may not work for you if you want it to be fully automatic.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot