Hi Jesse, I tried the pipeline script in first comment in Jenkins 2.73.3 and I was able to get back the environment variable contributed by Team Concert Plugin's Environment Contributor. It appears that env is getting rebuilt. Could you confirm this? Also it will help if you could provide the Jenkins issue through which this was fixed.
On Wednesday, October 5, 2016 at 8:25:46 PM UTC+5:30, Jesse Glick wrote: > > On Wed, Oct 5, 2016 at 7:04 AM, Sridevi Sangaiah > <[email protected] <javascript:>> wrote: > > Could there be any additional implementation that is required to > invalidate > > or refresh the environment variables, in case the env object was already > > constructed? > > And yes `env` caches variables after first use, to avoid performance > problems. There is not currently any provision to rerun > `EnvironmentContributor`s, nor any API in Jenkins for such > contributors to indicate that their result might have changed since > the last call. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/661205a8-7a53-437d-8c58-3c65c13ba26c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
