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

Schedule existing release in Bamboo

Hi ,

We would like to know if there any way to schedule existing release in Bamboo.

As of now  with existing functionality we can trigger the deployment job at any specific time but it will always pick up the latest successful build from either the custom branch or the default branch depending upon how triggers are configured.

We have a business case where only certified packages can be promoted to next environment , so scheduling of existing release remains very important point in Bamboo framework where anyone can schedule a certified existing release to higher environment.

please let us know in case this is achievable with some other Bamboo feature or its readily available to utilize.



Ashish Panwar

1 answer

Hi @Ashish Panwar,

You could potentially make use of Bamboo REST API ( and promote the build you are looking for creating the release / version you need. However, this should be scripted as a cron job, for instance.

Here is just an example, lets say you have a PROJ-PLAN and have ran 3 builds with it:

# Fire build execution for specified plan
# /queue/{projectKey}-{buildKey}

curl -k -u USERNAME \
-H 'X-Atlassian-Token: no-check' \
-X POST 'http://localhost:8085/rest/api/latest/queue/PROJ-PLAN'

Then, you decided creating a release from the 2nd build, called version2:

# Create deployment version for given deployment project.
# /deploy/project/{deploymentProjectId}/version

curl -k -u USERNAME \
-H 'X-Atlassian-Token: no-check' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-d '{"planResultKey":"PROJ-PLAN-2","name":"version2","nextVersionName":"version3"}' \
-X POST 'http://localhost:8085/rest/api/latest/deploy/project/1114113/version'

Then running the deployment by issuing the version:

# Trigger deployment for deployment environment and version.
# /queue/deployment?environmentId={environmentId}&versionId={versionId}

curl -k -u USERNAME \
-H 'X-Atlassian-Token: no-check' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-X POST 'http://localhost:8085/rest/api/latest/queue/deployment?environmentId=1212417&versionId=1376257'

Please, refer to for more information.

Kind regards,


Suggest an answer

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

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

195 views 4 6
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