Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42499

EnvActionImpl.ownerEnvironment cache never gets invalidated

      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.

          [JENKINS-42499] EnvActionImpl.ownerEnvironment cache never gets invalidated

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-29537 [ JENKINS-29537 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 106 (Web Link)" [ 15602 ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-33310 [ JENKINS-33310 ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: