Archiving the file only works if the parent job completes before triggering the child job. At least in my case, I'm using the Parameterized Trigger plugin as a build step, taking advantage of the built-in joining capability that it gives, and then want to perform some action depending on the success of all the child job (parent job fails if any of the child jobs fails).
So I don't have the luxury of archiving the properties file. Any way to pass a pointer to it in the parent job's workspace? Would need to be a URI, to include the node name, to handle the case of multiple builders. An alternative would be able to say "start this job with this property file" in the Parameterized Trigger plugin, where the Jenkins master would upload the file, then send it to the child process. It's things like this that make Jenkins awkward to use for complete workflows, where a continuous environment between jobs makes sense. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Share-environment-variables-between-jobs-tp2990985p4712982.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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
