AFAICT, Env-inject plugin injects vars in to a build, it does not get across to other build steps and it doesn't let you modify existing build vars etc.
Vivek Sent from my iPhone > On Jul 1, 2014, at 12:02 PM, Daniel Beck <[email protected]> wrote: > > I'm not a fan of env-inject, but isn't that what its build step basically > does when loading env vars from a .properties file? > >> On 01.07.2014, at 20:30, Vivek Pandey <[email protected]> wrote: >> >> As discussed on IRC sometime back about writing a plugin that lets you add >> new build environment variables or override a pre-defined or existing >> variables at each build step. >> >> I have a plugin implemented with these functionalities. >> >> Basically you can add set of variables at a build step and these will be >> carried over to the sub-sequent build steps. These variables can also be >> added/updated any any build step using Jenkins CLI command provided by this >> plugin. >> >> My GitHub id is vivek. >> Plugin name: "Build Env Propagator" >> Github repo name: envpropagator >> >> thanks, >> >> vivek. >> >> >> -- >> 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]. >> For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
