Bamboo Deployments Approved and Broken

Spot Support February 13, 2014

We're using Bamboo 5.3.0 and I would like to know the purpose of the "Approved" or "Broken" button options for each deployment release, specifically, the purpose of their current implementation.

The obvious problem is that there is no way to restrict/permission who can or cannot click on them. It's just a toggle button that anyone can click on. Should be that only specific groups (QA) or users can click on this.

So once the permissions are in place, then it would make sense to have only "Approved" releases be able to be deployed to the next environment (e.g. Staging is Approved, now we can deploy to Production) and alternatively, "Broken" release cannot be released (even to the same environment) until it becomes "Approved"

6 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Austin April 6, 2015

I'd really like to see this implemented as well, so I've created a feature request for it, please vote for it here: https://jira.atlassian.com/browse/BAM-15814

Serge Poulin March 6, 2017

Thanks Austin.

I did "+1" to your request with my comments.

Really hope this will make it into Bamboo.

2 votes
rsperafico
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 28, 2015

Hello,

Thank you for your question.

The Approved and Broken buttons are just flags that work as labels, but more exposed. They are not used anywhere in the logic, I am afraid.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

Kind regards,
Rafael P. Sperafico
Atlassian Support

Oliver D'Alton February 8, 2017

Yo, thanks for the explanation but seriously that button in Wak. You really should be able to trigger builds / deploys following that action or block builds missing that approval, seems like a great feature that was partially implemented

Like # people like this
Richard Cross February 8, 2017

"great feature that was partially implemented" .... yeah, well, welcome to Bamboo!

srikanth December 14, 2017

Will this feature/functionality will be implemented in future release of bamboo? I see many users (QA) who sees this functionality very useful.

Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2018

Hi!

Any plans go forward for fully implement this feature? 

 

Cheers,

Gonchik Tsymzhitov

0 votes
Sébastien Vermeille October 11, 2017

Same here we want our release manager be able to approve it and then it generate a final release -> deploy it on some platform and so on !

0 votes
Richard Cross November 27, 2014

+1 and setting to Approved or Broken should be able to trigger a subsequent action, e.g. tag/label source repository promote artifact internallly promote artifact externally (e.g. in Nexus)

0 votes
Daniel Lazdin May 21, 2014

Me too. Need to know how to block unapproved releases.

0 votes
Massimo Corà April 8, 2014

+1 This is something that also I have to figure out.

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events