-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.25 (on Windows Server 2008 R2 x64),
envinject 1.93.1, promoted-builds 2.27
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
[JENKINS-39497] No recursive expansion in promoted build
GMC Software Development B&R Corporate
created issue -
GMC Software Development B&R Corporate
made changes -
| Description |
Original:
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 ... {noformat} [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER {noformat} 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 |
New:
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 {noformat} Output2=E:\\Temp\\$PROMOTED_NUMBER {noformat} ... and the console shows ... {noformat} [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER {noformat} 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 |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |