-
Bug
-
Resolution: Postponed
-
Blocker
-
envinject-plugin 2.1.4
envinject-api-plugin 1.3
-
-
2.1.6
We have a global setting of JIRA_URL=jira.acme.com
In some jobs we override this in the "Prepare an environment for the run" section to JIRA_URL=jira-staging.acme.com
After upgrading to 1.24 this stopped working. The effective value as seen in shell scripts is jira.acme.com
Setting the value in a "Inject environment variables" build step also has no effect.
The only thing that has an effect is to set the value inside the shell script.
- is duplicated by
-
JENKINS-53229 Regression: Variables set in generateEnv are unset by the SECOND envInject
-
- Open
-
-
JENKINS-53213 Adjustments of ENV variables created by the EnvInject plugin are not carried over to new shell steps in a freestyle build.
-
- Closed
-
- relates to
-
JENKINS-14437 envinject fails to "really" set/override build parameters
-
- Reopened
-
-
JENKINS-47364 Existing variables not being substituted in Properties Content
-
- Resolved
-
- links to
[JENKINS-47370] Unable to override global envs after update to 2.1.4
Link |
New:
This issue relates to |
Labels | New: regression |
Priority | Original: Critical [ 2 ] | New: Blocker [ 1 ] |
Link | New: This issue relates to JENKINS-14437 [ JENKINS-14437 ] |
Remote Link | New: This issue links to "CloudBees Internal OSS-2517 (Web Link)" [ 20157 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Released As | New: 2.1.6 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |