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?
...roperties: -Dbamboo.bitbucket.cloud.use.workspace.api=true There are patches available for Bamboo versions 6.8.3, 6.9.2, and 6.10.5 on the bug report that add support for the System Property. T...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events