We do this all the time. After checking out, run a script builder that generates your environment changes in the form of a properties file. In Unix, you might have lines like:
rm -f env.properties touch env.properties echo "BRANCH = `some_command_that_calculates_branch` >> env.properties echo TIMESTAMP = `date` >> env.properties The "rm" and "touch" is to make sure that the file exists and is empty. The >> is to append (if you just use '>', you'll clobber all the lines you wrote earlier) Your next build step is to inject environment variables from env.properties. --Rob Mandeville Litle & Co. -----Original Message----- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of JR Cary Sent: Wednesday, December 04, 2013 11:59 AM To: jenkinsci-users@googlegroups.com Subject: How to inject environment vars just after the master checkout? I would like to run a script on master after the SCM checkout, as the script is in the repo, to set an environment var that propagates to all the slaves. It seems that EnvInject cannot do this? Or am I missing something? Thx.....JC FYI, the purpose of this is: I have an svn repo into which I checkout a git subrepo that I want to update to the same state across all builds. -- 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/groups/opt_out. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer. -- 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/groups/opt_out.
