You may want to consider using the EC2 plugin, to let it handle starting/stopping your slave instance and sending the job(s) to be run there automatically.
The method you are using, though, is the most effective way to do what you are doing now. ----- Original Message ----- From: [email protected] To: [email protected] Cc: [email protected] At: Feb 21 2013 07:47:12 In case anyone has a similar requirement as mine, I ended up doing the following: >From the shell script which starts the EC2 instance I write to file the host name of the new instance. I use the EnvInject<https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin> plugin to read the host name from the file and set it as environment property. >From there I can reference it in the next job, using the Buld Flow plugin and the Groovy DSL: serverup = build( "JOB 1" ) out.println "host: " + serverup.envVars["host"] ... Probably not the most elegant solution, but it does the job. Any suggestion that allows me to do the same without going through a file is welcome! On Thursday, 21 February 2013 11:38:05 UTC+1, [email protected] wrote: > > Yes, even though I would like to use the Build Flow plugin to orchestrate > the flow. > Still, it is unclear to me how I can assign a Jenkins env variable from a > shell script. > > L > > On Thursday, 21 February 2013 10:45:27 UTC+1, ogondza wrote: >> >> Hi, >> >> This seems to do what you want >> https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin. >> >> >> -- >> oliver >> > -- 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/groups/opt_out. -- 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/groups/opt_out.
