I'm thinking a static initialization block might be better. One is used in the email-ext plugin to set some system properties, this would make sure the property/env variable was set before accessing the third party library.
On Tue, Jul 16, 2013 at 5:48 PM, Kannan Manickam <[email protected]> wrote: > Check out the envinject plugin: > https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin I think it > might do what you want. > > > On Tue, Jul 16, 2013 at 5:30 PM, Vinod Kone <[email protected]> wrote: > >> Hi, >> >> I'm writing a plugin that uses a third party library that expects an >> environment variable to be set when used. Is it possible for the plugin >> itself to be able to set this dynamically, so that when jenkins master >> starts (or loads the plugin) this env variable is set and available to the >> library? >> >> Thanks, >> >> -- >> 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/groups/opt_out. >> >> >> > > -- > 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/groups/opt_out. > > > -- Website: http://earl-of-code.com -- 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/groups/opt_out.
