Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo deployment project conditionals Edited


I'm configuring Bamboo for deployment to different environments (development, qa, staging, production). I'm looking for a way to have a condition to exist before enabling a build, for example if a certain JIRA ticket is closed then (and only then) we should deploy in production.

Currently I have a separate project for each environment, each with its build plan. I have granted specific users the ability to run a build&deploy (since specific groups should be able to deploy only on their specified environments), but the idea would be to have an OK from several people before enabling the production deployment.


Any suggestion regarding how to accomplish such a thing is much appreciated.

Kind regards.

1 answer

1 vote

Hi Nicolas,

I think you'll not be able to do that directly in Bamboo, the easiest way would be to set these conditions in JIRA and then trigger the deployment calling a Bamboo REST API using a Webhook

Hello Gabriel,

Thanks for your reply. The thing is, we mustn't run the deploy task automatically. Your reply did give me an idea: we could set the conditions in JIRA and then call the bamboo API to mark the release as 'approved' by user JIRA, and then put a script that checks if user JIRA has approved the release. Does that make sense?


Kind regards.

Hi Nicolas,

Yes, your idea makes sense. I never tried to implement this before, but I think the most challenging thing will be to get the {deploymentVersionId} from the specific release you want to edit.

As you can see, the API endpoints require this info:

Show current status:


Change status:

http://<bamboo URL>/rest/api/latest/deploy/version/{deploymentVersionId}/status/UNKNOWN|APPROVED|BROKEN|INCOMPLETE

Interesting resource:



Like Poojatr likes this


I tried by https://<bamboo URL>/deploy/viewDeploymentVersion.action?versionId=87648402

But the number 87648402, is not the deploymentVersionID, 

Did you get any method to extract the deploymentVersionID?

Thank you

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center - Early Access Program

G’day Bamboo customers, The wait is almost over! We are in the final stages of work on the first release of Bamboo Data Center, our self-managed enterprise offering of Bamboo. This Data Center offe...

1,008 views 0 16
Read article

Community Events

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

Events near you