Project: bamboo
Issue BAM-9674: When retrying a release with the release management plugin, default plan variables displayed are not used in the build
We have a bamboo plan for our "release" which runs the maven-release-plugin to actually release our software. We define the plan with two plan variables: "thisVersion" and "nextVersion". Steps to reproduce: # Go to a JIRA version for the project we want to release, go to the "release" tab, and click to release this JIRA version using the bamboo release plugin # select "release with new build" and choose the correct bamboo plan (the release plan with the custom variables) # Click the link to type a value for the variable "thisVersion" and enter a value of 1.1.0 # Click the link to type a value for the variable "nextVersion" and enter a value of 1.2.0.M1-SNAPSHOT # Click Release \\ The plan will fire. If the plan fails, then it is displayed as failing in JIRA and there is a button to "retry" \\ # Click Retry and the same release plugin popup will be displayed with the previously selected values already filled out except for these problems: * *while there are two rows for each of the two plan variables we previously input, the variable name in the dropdown is the same for each*. It lists both variable names as "nextVersion", even though we originally selected the drop downs as "thisVersion" for the first, and "nextVersion" for the second. ** Note that the correct values, however, are still present in the text boxes. Thus when you see the screen (and I forgot to get a screenshot) you see in the first row a select box with "nextVersion" but with a value of 1.1.0. And the second row has (again) "nextVersion" in the drop down and the text box value of 1.2.0.M1-SNAPSHOT. Thus, it persisted the text box values correctly but not the drop down selections correctly. * If you only change the value of the first drop down -- i.e. change the first drop down from "nextVersion" to "thisVersion" (which is how we originally filled it out) and don't touch the second drop down box at all -- then it will _only_ set the "thisVersion" plan variable (the drop down that we physically clicked and changed). It will _not_ submit the "nextVersion" variable value to the plan, despite appearing exactly as it did when we originally filled out the form. This of course made my plan fail a second time as the maven-release plugin needs the "nextVersion" value, and since I don't have a default maven fails because the next version is "" (empty string). I went back to the Jira Version -> release page and "retried" a third time. Again I was presented with a form that had both drop downs displayed as "nextVersion". I clicked the first row drop down and changed it to to the correct "thisVersion" variable. Then I clicked the second row (currently "nextVersion"), deliberately changed it to "thisVersion" and then clicked again to change it back to "nextVersion". I left the text box values alone -- as they were already correct. I submitted this and it worked perfectly. Thus, by clicking the second row dropdown and changing it and changing it back is a valid workaround. This seems pretty minor as there is an easy workaround and it seems to only be a problem whenever a release build fails, which is probably rare.
Story points: 2