PR keys / environment variables are never set

[Joachim Schiele]

Hey,

there are a few pull request related keys:

• bamboo.repository.pr.key
• bamboo.repository.pr.sourceBranch
• bamboo.repository.pr.targetBranch

They are explained here:

https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html

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 ${bamboo.repository.pr.sourceBranch} but then I get:

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

Probably related to https://jira.atlassian.com/browse/BAM-13017

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!

Regards,

Joachim Schiele

[George Constantine]

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.