Eric Wood (2014-06-05 16:15):
Can I set global variables and then use in jobs without using parameterized builds. This forces me into a manual response mode that does not work in my scenario.
We use a trick to save data into files (`echo "1" > ./exitStatus.jenkins`) and then read in another build step (exitStatus=`cat ./exitStatus.jenkins`). AFAIK there is no other way (other then exporting variables which seem like an overkill and would not be safe as it would break job isolation).
Cheers, Nux. -- 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/d/optout.
