Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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 @ashishpanwar,

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

Atlassian Community Events