Hi Dirk, I am facing the exact same problem. The EnvInject step doesn't seem to run when the build fails - and therefore I can't get the injected variables for my ext-email step.
Did you find a solution or workaround to this problem? Thanks, Ambar On Thursday, 12 September 2013 14:08:36 UTC+5:30, Dirk Heinrichs wrote: > > Hi, > > I need some environment variables produced by a build step in a > post-build action (namely: EmailExt). Therefor, the build step writes a > properties file and a second build step (EnvInject) injects the > variables from that properties file. Works fine as long as the first > build step doesn't fail. > > In case of failure, the EnvInject build step isn't executed anymore, so > that the environment variables are not available in the post-build > action. How do I propagate environment variables to post-build actions > in case of a failed build? > > Thanks... > > Dirk > -- > > *Dirk Heinrichs*, Senior Systems Engineer, Infrastructure > *Recommind GmbH*, Von-Liebig-Straï¿œe 1, 53359 Rheinbach > *Tel*: +49 2226 1596666 1149 > *Email*: [email protected] <javascript:> > <mailto:[email protected]<javascript:>> > > *Skype*: dirk.heinrichs.recommind > www.recommind.com <http://www.recommind.com> > > > http://www.recommind.com > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
