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

Can I pass multi customRevision on "/queue rest api"?

Dear All


My Bamboo plan has more than one SVN Repository.

Is it possible to pass the customRevision value per repository to the "/queue rest api"?


※ "/queue rest api" specification has only one customRevision.


Help me..


Best Regards

1 answer

1 vote

Hi, I found this Atlassian Cummunity post: [].

It provides this as a solution (example revision number 63781):

curl -X POST  http://{bambooBaseURL}/ajax/runParametrisedManualBuild.action?os_authType=basic&planKey=MYCHANGSETBUILD&customRevision=63781

You may give it a try. Hope it makes the trick for you!

Cheers, Gerhard

Thank you for your kind reply.

My problem is that one plan has more than one REPO and I want to pass the REVISION for each REPO through the "/ QUEUE REST API".


a plan - a1 repo

           - a2 repo

           - a3 repo


I want set a1, a2, a3 customRevision.


Is it possible in the way you told me?

I don't believe it'll work like that, but just for one SVN repo.

I found another Atlassian Community post that comes up with another idea which I give more chance to work as you need it. Base is to not utilize a Bamboo "Source Checkout Task" but instead a "Script Task" to retrieve SVN sources.

From there you might do the below, 3 times, for repo a1, a2 and a3 respectively:

svn co repoUrl -r $targetRevisionX

You'd need to think about thing like authentication of your repoUrl that you get automatically by use of the  "Source Checkout Task", just as a heads up.

The Community article is here:

Hope this helps you better!

Sorry, same post, but further down. Too close to weekend ;-)

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 ...

190 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