How do you refer to a Branch's artifact if you do not know the branch "number" beforehand?

I'm trying to setup a build that pulls artifacts from several other parent builds and am having some trouble figuring out how to correlate the branch "id" for a specific plan (the integer appended to the plan key) with the branch name. The variable $ seems to only contain the branch name from the version control repo.

For example, I have two branches, master and release. master's "id" is 0 and the Plan name looks like MYPLAN0 while release's id is 1 and the plan name looks like MYPLAN1.

Is there a way to easily refer to branches in Bamboo by the version control branch name? Is there some variable that makes it easy to generate a URL to the corresponding branch of another Plan? Dependencies are capable of being linked based on plan name, but I can find no way to actually pull in artifacts.

Ideally, it'd be as simple as MYPLAN/branch/master or MYPLAN/branch/release and then all routes normally following MYPLAN could instead follow the branch name.

3 answers

1 accepted

Oh, and there is a ticket in the Bamboo issues tracker that you might be interested in: - basically it is the same feature request you would like to have, isn't it? Might be a good idea to add yourself as a watcher/voter to that issue.


I'd try a REST api to obtain a proper branch-plan. AFAIK there is REST resource in Bamboo that for a given master-plan key and for a given branch name will return you in the response the relevant plan-branch key. Probably you could use that to craft the necessary urls by yourself... or maybe not.

The REST resources I'm thinking of are:

* plan/{projectKey}-{buildKey}/branch/{branchName}

* /plan/{projectKey}-{buildKey}/vcsBranches


More or less that ticket would do what I'm asking for, yes. Will add myself as a watcher/voter.

Guess I'll try the API too.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
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,064 views 0 5
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot