We have a release process that moves from "CI" up through different environments and ends in "Beta" and then "Live".
The build artifacts in "CI" are generated by changes to the _master_ branch of our repository. Each of those builds generates a new build number.
To move from one environment to the next (e.g. "Beta" to "Live") is not automated. We manually click "Deploy", select the environment (e.g. "Live") and select the build version.
In other words, say version `1.5` is "CI" and `1.0` is in "Beta". When I want to move `1.5` to "Beta", I:
How can I accomplish the steps described above using a scheduled trigger in the "Live" environment?
The "Trigger configuration" section only shows options related to the repository branches, not already generated build artifacts.
I do not want to deploy latest build from master or any other branch. I want to promote the build currently in Beta to Live.
Scheduled deployments are a popular feature request, but unfortunately not available yet - please watch and vote for the following related issues to further raise Atlassian's awareness of this requirement:
Glad it helps @William King - please also 'accept' my answer as solution via the checkmark on the left side so that it doesn't show up as unanswered anymore, thereby keeping others and myself focused on and motivated to assist with new questions :) - thanks!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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