Low Description
After upgrading our installation of Bamboo to 4.3.1, I'm finding a number of plan branches which no longer have the expected contents of bamboo variables.
To work around deficiencies in previous versions of Bamboo, the source repository in these plans reads:
https://svnhost/svnpath/project/${bamboo.repoprepend}${bamboo.branch}
Our usual project layout is:
project/trunk <- main development
project/branches/X.Y.Z <- particular branch
In order to have the same plan be able to build the trunk and the branches, the plans were set up with the 'repoprepend' variable set to 'branches/'. The only branch in each plan to override this variable was the 'HEAD' branch, which set 'repoprepend' to '' and 'branch' to 'trunk'.
After the migration, all the 'HEAD' branches failed, because Bamboo was unable to construct a valid svn path. Configuring the Branch and trying to add the Branch override of the 'repoprepend' variable to '' or anything else resulted in a message:
This Plan already contains a variable named repoprepend
Smart Bamboo, there is already a variable named 'repoprepend'. But you're not listing it in the branch variable listing, and not letting me override it. You're also referring to the 'Plan' instead of the 'Branch'. No cookie for you.
The only cure is more cowbell. Wait, that's not it. Deleting the branch and recreate it, with 'repoprepend' containing '' works, but that gets tiresome to do through the UI.
Please do the Right Thing in properly migrating Bamboo variables with empty strings. And fix that error message to refer to 'Branch' instead of 'Plan'.
Workaround
A workaround to this bug if you don`t intend to have a variable with empty values is to update via the database using the command below:
update variable_definition set variable_value="some values" where variable_key = "name_of_variable";
You will need to restart Bamboo for the changes to take effect. Also remember to take a backup before running any command on your database.
