[JIRA] (JENKINS-39497) No recursive expansion in promoted build

[gmc-de...@br-automation.com (JIRA)]

Title: Message Title

GMC Software Development B&R Corporate created an issue   Jenkins / JENKINS-39497 No recursive expansion in promoted build Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2016/Nov/04 9:12 AM Environment: Jenkins 2.25 (on Windows Server 2008 R2 x64), envinject 1.93.1, promoted-builds 2.27 Priority: Major Reporter: GMC Software Development B&R Corporate We have determined a problem with using an environment-variable, which are defined by using another variable (Ie. recursive expansion) in a promoted build. Following (minimal) scenario: a) Inject environment variable Output2=E:\\Temp $PROMOTED_NUMBER ... and the console shows ... [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER b) Using this variable as Remote File Location in ArtifactDeployer (I.e., $Output) will use "E:\Temp\$PROMOTED_NUMBER" as destination-folder (what was not our expectation). If we configure "E:\Temp\$PROMOTED_NUMBER" as Remote File Location, this will be expanded (eg.) "E:\Temp\42". Sorry - I'm not sure, whether this (assumed) expansion takes place in older versions of this plugin(s) or this behaviour is a regression ... Best regards from Salzburg, Markus Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.