Hi,
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:
http://path/to/repository#${bamboo.tagToBuild}
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?
Cheers,
Adam
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 https://jira.atlassian.com/browse/BAM-9908 in the Bamboo bug tracker to investigate this issue further.
regards,
PS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
moved... :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.