Mercurial repository URL - build variables


We're using Bamboo 3.2 and are trying to build a specific Mercurial tag or changeset for our release builds. The Repository URL on the source repository configuration screen supports the #revision syntax, which is great. What I would like to do is parametize this using the bamboo build variables.

Something like the following:


However I get a malformed url error message when I attempt to do this. To me, this seems the simplest way to achieve builds based on a particular tag, but I'd like to know if we're trying to do this the wrong way.

Can anyone please advise how they have overcome with this particular problem? Or is this something unique to us, and possibly indicating that we should be following a different process?



2 answers

1 accepted

Use the tag in the branch field instead.

i.e. :

repositoryUrl = http://path/to/repository

branch = ${bamboo.tagToBuild}

Seems to me like a bug in Bamboo. I've raised in the Bamboo bug tracker to investigate this issue further.



Thanks PS.

What's the chances of it being addressed in 3.3? And are you aware of any work arounds that will help us out for now?

what will happen, if you use following:

repositoryUrl = http://path/to/repository

branch = ${bamboo.tagToBuild}

Would it work?

ad chances in 3.3 -> I don't think it would be adressed in 3.3. Maybe in 3.3.1 I'd say.

Doh! Looks like I didn't read the documentation properly. It quite clearly says that you can place a tag in the branch field.

Thanks for your help - specifying a bamboo build variable in the branch field works a treat!

If you move the comment into an answer I can mark it as accepted.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,788 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you