Yes! I had to echo all the environment variables into the properties file
using the format:
echo "PARAM1=${PARAM1}" >> myprops.properties
(make sure your first echo has ">" instead of ">>", so the file gets
initialized)
The child build then had all those values!!!
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Share-environment-variables-between-jobs-tp2990985p4712995.html
Sent from the Jenkins users mailing list archive at Nabble.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/d/optout.
