EnvActionImpl.ownerEnvironment cache never gets invalidated

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Jesse Glick
            Reporter:
            Jesse Glick
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: