Cool. Thanks for sharing.
I just found another way that also seems to work well - sharing it in case
it helps someone else... sorry if it's a bit verbose.
When I was trying the EnvInject plugin, I was setting the EnvInject
properties file like this: "mailing_list = buildf...@mydomain.com" in m
Am 06.01.2014 00:59, schrieb ambar s:
> Did you find a solution or workaround to this problem?
Yes. You shouldn't let the build fail. Instead, each build step should
set a status variable which indicates wether it has failed or not. Then,
add a final env-inject (if needed), followed by another bu
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
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.
