environment variable name being set to 'undefined' when passed from Jira to Bamboo under certain cercumstances

XMLWordPrintable

    • 7.02
    • 2
    • Severity 3 - Minor

      Summary

      Plan variables passed from Jira to Bamboo; One variable will be set to 'undefined' as the variable name instead of properly overrighting the variable value as expected.

      When sending from Jira to Bamboo:
      variable = xyz
      cvariable = abc

      Bamboo receives
      variable = xyz
      undefined = abc

      Environment

      • Bamboo
      • Jira Server
        • Unknown if the bug affects Jira Cloud

      Steps to Reproduce

      1. Configure a build plan with at least one Build linked to a Jira issue
      2. Add the 4 variables above as Plan variables
      3. Enable DEBUG logging in Jira
      4. Create a Version in Jira
      5. Release the version, overriding the variables: 
        testing : bam
gtesting : boo
foobar : foobar
testingh  : test

      Expected Results

      variables set in Jira release sent properly to Bamboo

      Actual Results

      The below is shown in the logs:

      jira HTTP Log
      2017-12-15 20:24:24,009 http-nio-9080-exec-5 DEBUG admin 1224x1133x1 d5y7ix 127.0.0.1 /secure/SubmitBambooRelease.jspa [o.apache.http.wire] http-outgoing-86 >> "bamboo.triggerReason.jiraProjectName=Elias+Test&bamboo.triggerReason.jiraVersion=v4&bamboo.variable.foobar=foobar&bamboo.variable.undefined=boo&bamboo.variable.testingh=test&bamboo.triggerReason.jiraUsername=admin&bamboo.triggerReason.jiraProjectKey=ET&bamboo.triggerReason.jiraBaseUrl=http%3A%2F%2F<bamboo-url>%3A9080&bamboo.variable.testing=bam&bamboo.triggerReason.jiraVersionId=10003&bamboo.triggerReason.jiraUserDisplayName=Elias+Zeidan&bamboo.customTriggerReasonKey=com.atlassian.bamboo.plugin.jira%3AjiraReleaseTriggerReason&bamboo.customPlanTriggerKey=com.atlassian.bamboo.plugin.jira%3AjiraReleasePlanTrigger"
      Bamboo Build Log
      Custom variables
Name	Value
jira.projectKey	ET
jira.version	v3
foobar	foobar
jira.projectName	Elias Test
testingh	test
testing	bam
jira.username	admin
jira.baseUrl	<jira-url>
undefined	boo

      Workaround

      Currently the only workaround is to change the variable names to be dissimilar from each other.

            Assignee:
            Unassigned
            Reporter:
            Robert W (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: