Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Noting 2.1.6


  • Only previous environment variables are available for polling
    Some plugins provide polling mechanisms (such as SCM plugins, XTrigger plugins, ...) and you want to use injected environment variables in form fields of these plugins. Unfortunately, injected environment variables are processed only at build time therefore after the build is scheduled. Therefore, we can't access environment variables configured within the job. However, previous injected environment variables (from the previous build) are retrievable (implemented for example in the XTtrigger plugins). For the other plugins, authors are free to add the envinject-lib library dependency in their plugins in order to provide the ability to use environment variables given the EnvInject plugin.


2.1.6 (Jun 07, 2018)

Release with minor improvements in the codebase:

  • (info) PR #131 - refactor the code to prevent warnings about attempts to (de-)serialize anonymous classes in Jenkins 2.107.2+
  • (info) PR #129 - update the plugin so that it can be tested with Plugin Compat Tester
  • (info) PR #130 - fix typo in the Groovy script variable documentation

2.1.5 (Oct 13, 2017)

  • Add compatibility notice for issues reported in 2.1.4