-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.60.1
OS - CentOS release 5.10
EnvInject Plugin 2.1.3
When using a +build paramete+r in the Properties Content field of the Inject environmental variables build step the plugin adds a '=' sign at the end.
Example:
- Define a Text Parameter called: ENV_VARS_TEST
- Add a build step "Inject environmental variables"
- Set Properties Content to ${ENV_VARS_TEST}
- Start a Build and set the ENV_VARS_TEST Build Parameter to $FOO_VAR=BAR
The Build Output:
[EnvInject] - Loading node environment variables.
[EnvInject] - Injecting environment variables from a build step.
{{[EnvInject] - Injecting as environment variables the properties content }}
$FOO_VAR=BAR=
See the "=" added at the end of the line.
Same happens if I define "FOO_VAR=BAR" (without the $ sign) in the build parameter. Then I get
[EnvInject] - Injecting as environment variables the properties content
FOO_VAR=BAR=
When I add the string "$FOO_VAR=BAR" directly into the "Inject environmental variables" build step "Properties Content" section I get the expected "$FOO_VAR=BAR", like so:
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties content
$FOO_VAR=BAR
As soon as I put a build parameter into the Properties Content section I get this behavior with the added "=" at the end.
I was also able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep
.
[JENKINS-45400] EnvInject Plugin adds '=' sign at the end if 'Properties Content' is referencing a Build Parameter
Steffen Thumser
created issue -
Steffen Thumser
made changes -
| Description |
Original:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* The Build Output: [EnvInject] - Loading node environment variables. [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content $FOO_VAR=BAR= See the "=" added at the end of the line. Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get [EnvInject] - Injecting as environment variables the properties content FOO_VAR=BAR= When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:** [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content $FOO_VAR=BAR I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep. |
New:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} {{ [EnvInject] - Loading node environment variables.}} {{ [EnvInject] - Injecting environment variables from a build step.}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:**}} {{ [EnvInject] - Injecting environment variables from a build step.}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
Steffen Thumser
made changes -
| Description |
Original:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} {{ [EnvInject] - Loading node environment variables.}} {{ [EnvInject] - Injecting environment variables from a build step.}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:**}} {{ [EnvInject] - Injecting environment variables from a build step.}} {{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
New:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} \{\{ [EnvInject] - Loading node environment variables.}} \{\{ [EnvInject] - Injecting environment variables from a build step.}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:**}} \{\{ [EnvInject] - Injecting environment variables from a build step.}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
Steffen Thumser
made changes -
| Description |
Original:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} \{\{ [EnvInject] - Loading node environment variables.}} \{\{ [EnvInject] - Injecting environment variables from a build step.}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:**}} \{\{ [EnvInject] - Injecting environment variables from a build step.}} \{\{ [EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
New:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. (sorry for the messed up formatting.. something went wrong here...) +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} [EnvInject] - Loading node environment variables. [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} [EnvInject] - Injecting as environment variables the properties content {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:}} [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
Steffen Thumser
made changes -
| Description |
Original:
When using a build parameter in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '=' sign at the end. (sorry for the messed up formatting.. something went wrong here...) +Example:+ # Define a Text Parameter called: _ENV_VARS_TEST_ # Add a build step "Inject environmental variables" # Set Properties Content to _$\{ENV_VARS_TEST}_ # Start a Build and set the _ENV_VARS_TEST_ Build Parameter to *$FOO_VAR=BAR* {{The Build Output:}} [EnvInject] - Loading node environment variables. [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. {{Same happens if I define "FOO_VAR=BAR" (without the $ sign). Then I get}} [EnvInject] - Injecting as environment variables the properties content {{FOO_VAR=BAR=}} {{ }} {{When I add "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "*$FOO_VAR=BAR*", like so:}} [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content {{$FOO_VAR=BAR}} {{I was able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep.}} |
New:
When using a +build paramete+r in the *Properties Content* field of the *Inject environmental variables* build step the plugin adds a '*=*' sign at the end. +Example:+ # Define a Text Parameter called: ENV_VARS_TEST # Add a build step "Inject environmental variables" # Set Properties Content to $\{ENV_VARS_TEST} # Start a Build and set the ENV_VARS_TEST Build Parameter to $FOO_VAR=BAR +The Build Output:+ {{[EnvInject] - Loading node environment variables.}} {{[EnvInject] - Injecting environment variables from a build step.}} {{[EnvInject] - Injecting as environment variables the properties content }} {{$FOO_VAR=BAR=}} See the "=" added at the end of the line. Same happens if I define "*FOO_VAR=BAR*" (without the $ sign) in the build parameter. Then I get {{[EnvInject] - Injecting as environment variables the properties content}} {{FOO_VAR=BAR=}} When I add +the string+ "$FOO_VAR=BAR" +directly+ into the "Inject environmental variables" build step "Properties Content" section I get the expected "$FOO_VAR=BAR", like so: {{[EnvInject] - Injecting environment variables from a build step.}} {{[EnvInject] - Injecting as environment variables the properties content}} {{$FOO_VAR=BAR}} As soon as I put a build parameter into the Properties Content section I get this behavior with the added "=" at the end. I was also able to reproduce this in a fresh free-style created project with just this and a shell-echo buildstep . |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |