Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Get name of repository branch from Source Code Checkout task

A Stage in a Bamboo Build Plan contains a Source Code Checkout task which checks out code from one of the Bitbucket repository branches that is linked to the Bamboo Build Plan. 

What specifically do I need to type or do in order to get the name of the repository branch that was checked out by the Source Code Checkout task? 

I have typed

`echo ${bamboo.planRepository.branchName}` 

in a subsequent Task inside the same Stage in the same Build Plan, but this just prints out the name of the default branchName for the entire Build Plan, which is different from the specific branch that was just checked out by the specific Source Code Checkout task about which I need information.

1 answer

`echo ${bamboo.planRepository.<position>.branchName}` 

<position> : position of the repository on plan's repository list (starting with 1 for default repo)

You did not answer the question..  The line of code you gave only supplies information about the Plan-level links to repositories.  By contrast, this question asks how to determine which of those repositories is checked out by a specific Source Code Checkout task in the specific Job.  My question assumes you do not already know the answer.  Your reply assumes that the script already knows the answer because if the script knows the value of the <position> variable, then the script practically knows the rest of the answer. 


Can you suggest an approach that utilizes Job-and-Task-level variables?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events