Details
-
Type:
Bug
-
Status: Reopened (View Workflow)
-
Priority:
Blocker
-
Resolution: Unresolved
-
Component/s: envinject-api-plugin, envinject-plugin
-
Labels:
-
Environment:envinject-plugin 2.1.4
envinject-api-plugin 1.3
-
Similar Issues:
-
Released As:2.1.6
Description
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.
Attachments
Issue Links
- 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
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Labels | regression |
Priority | Critical [ 2 ] | Blocker [ 1 ] |
Link | This issue relates to JENKINS-14437 [ JENKINS-14437 ] |
Remote Link | This issue links to "CloudBees Internal OSS-2517 (Web Link)" [ 20157 ] |
Assignee | Oleg Nenashev [ oleg_nenashev ] |
Assignee | Oleg Nenashev [ oleg_nenashev ] |
Assignee | Oleg Nenashev [ oleg_nenashev ] |
Released As | 2.1.6 | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Fixed but Unreleased [ 10203 ] |
Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Link | This issue is duplicated by JENKINS-53229 [ JENKINS-53229 ] |
Link |
This issue is duplicated by |
Confirmed here, after reverting to 2.1.3 all the problems gone. 2.1.4 need more testing.