How-to trigger a bamboo plan with a specific revision number

[Maximilian Friedmann]

Hi there,

when our svn repository receives a code change, it automatically triggers our Bamboo 3.3 instance. Some of the plans executed by a commit are dependent on each other and have to be built upon the same revision number. Unfortunately, sometimes a "trigger" needs more than a second and the revision number changed in between, so even if it looks like Plan A, Plan B and Plan C are triggered at the same time, they have different revision numbers.

Is there a possibility to tell Bamboo explicitly which revision to use? I tried it via rest and

https://bamboo/api/latest/queue/TEST-TEST?stage&executeAllStages&custom.svn.revision.number=6699

but it seems like its not working.

[James Dumay]

Hi Maximilian,

As long as the default repository shares the same subversion URL on both plans, Bamboo will automatically force the child plan to build from the parents revision.

As for the variable, setting this when triggering plans does not currently work. There is a ticket to improve this situation by allowing you to build from a custom revision number - please watch and vote for it.

Thanks
James

[Maximilian Friedmann]

Thx for the link, placed my vote ;-)