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

PR keys / environment variables are never set


there are a few pull request related keys:


They are explained here:

In our instance they never get set. I tried to access them using the: 'set' or 'export' on the script running in the bamboo build setup but they are not there.

I've also tried to access them using:

echo ${} but then I get:

${bamboo.planRepository.integrationBranch.branchName}: bad substitution

Probably related to

What can I do in order to distinguish between:

  • develop (our master branch)
  • any-feature-branch (no PR yet made)
  • any-feature-branch (but with a PR active)

I have a hunch that all feature branches are treated as potential PRs as creating a PR from a normal branch never would rebuild that source code again.

Hope someone can help me!


Joachim Schiele

1 answer

I am having the same issue, with all your mentioned keys.

We have a specific plan to run linters and code decorators for BitBucket PRs, and while the jobs get created and triggered on PR creation, the metadata doesn't exist.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events