AFAIK it's currently jenkins limitation that you can't bind sequence of jobs to one slave. I hope something will change after Cloud API improvements. All that you can do it just create a static slave in EXCLUSION mode (run only tied jobs), assign label, bind job to this label.
On Tuesday, April 28, 2015 at 6:42:50 AM UTC+3, gaurav kodmalwar wrote: > > Hi All, > > I have configured Jenkins for executing multiple SAS jobs sequentially > but libraries defined in first job being used by another job however > second jobs unable to identify those libraries. When I redefined > libraries in second job then issue got resolved. This issue doesn't > come up if I run same job in windows task scheduler. I suspect that > Jenkin is executing all jobs in a new sessions, how can I configure to > run all sequential jobs in a single session? > > By the way, I am calling my sas jobs through windows batch and that > windows batch call is configured in Jenkin\Task Scheduler. In Jenkins, > I selected option "Execute Windows Batch Command" and provided > following code: > D:\SAS\SASFoundation\9.4\sas.exe -sysin D:\spa\MasterDriverMain.sas > > MasterDriverMain.sas calls multiple sas jobs & takes care of looping etc. > > Thanks in advance. > > Gaurav > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/14cea02c-7216-4073-b48d-99a9572b98b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
