-
Bug
-
Resolution: Fixed
-
Major
Once env.PROP is evaluated, or DefaultStepContext loads environment variables, EnvActionImpl.getEnvironment caches ownerEnvironment and will not call Run.getEnvironment again for the same build. This means that an EnvironmentContributor which, for example, pays attention to an Action that might be added during the build will not have a visible effect.
Removing the cache is easy, but there is some performance implication.
- relates to
-
JENKINS-33310 Jenkins Pipeline (Workflow) support for HockeyApp plugin
- Resolved
-
JENKINS-29537 EnvironmentContributingAction compatible with Workflow
- Resolved
- links to