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
Hi Atlassian community.
We have BitBucket, Bamboo and Jira.
Everything works fine. But as we were looking at our work flows, we noticed that you can limit the transition from one state, to another, to certain users. Like for product owners, who need to approve certain steps of the work flow.
We would like that the deployment to a production server, is limited by what state the task(s) associated with the build is in. So if a commit has been tagged with myproject-227, then this task need to be in "Tested and approved for production" state, before it is allowed to be deployed. Likewise, commits with no tags would never be deployable.
I realize that a given commit would potentially be able to point to a random task in the right state, unless of course you have a solution for the above, as well as this potential pitfall.
That functionality does not exist in Bamboo at the moment. You can however write a custom app for Bamboo that does that using the Pre-Build Action module that fails the build:
There are other "before" modules that you can take a look too:
Thank you for the swift answer. I guess we are not looking for pre-build trigger, but rather for pre-deploy trigger. This way we can build and deploy to our testserver, and then we could potentially trigger a pre-deploy script before deploy on production server.
Do you see any possibilities for this?