we have been using plan branch builds for some time and used the shortPlanName as a nice variable that contained the branch label, to construct compound filenames.
in the latest release this variable has changed to not include the branch name, but only contain the plan name?
is this a bug or feature :). ive got around this by doing
oldShortPlanName=${bamboo_planName##* }
its a bit of a pain, the previous implementation IMHO is better
Hello @Ian Underhill ,
The previous behavior was not the correct one and was a BUG being tracked: shortPlanName contains branch name for plan branches
As this was resolved on Bamboo 6.10.2, this behavior has changed since.
Currently, Bamboo doesn't have a variable that retrieves the branch name; however, there's an open feature request for this: Variable to get plan branch name.
Also, we can see that Daniel Santos suggested a workaround for Linux script tasks, which uses the planName variable:
bamboo_planBranchName = ${bamboo_planName##* - }
I hope it helps.
You can use this type of variable in a script that is run on the remote agent.
So add a script step to your task. this is obviously a remote agent running Unix with bash
#!/bin/bash
oldShortPlanName=${bamboo_planName##* }
echo ${oldShortPlanName}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks I figured it out. For those interested.
I used the shortname to tag docker images, now Im using bamboo_planRepository_1_branch which sometimes has a / in the branch name which is not compatible with docker tags to resolve I replace / with _
#/bin/bash
docker build -t APPNAME:${bamboo_planRepository_1_branch//\//_}-{BUILDNUM}
@Ian Underhill thank you really saved me here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.