There are many ways to "skin this cat" so to speak - various cloud plugins, or things like docker can do this.
If you are thinking vagrant and VMs on demand, docker pipeline or one of the docker plugins could help with this (as it can quickly create containers as needed, but for the cost of one persistently running vm to host the docker daemon, or if you are on linux, there is no overhead really). On Monday, April 4, 2016 at 8:21:58 PM UTC+10, David Aldrich wrote: > > Hi > > > > We want to run a matrix build of a job across a set of Virtual Machines > that run on a single server. The VMs use a lot of resources so we don’t > want them to be up concurrently. > > > > Is it possible for Jenkins to bring up a VM before running a job and then > take it down afterwards, then bring up another VM and run the job again? > > > > Perhaps using Vagrant? > > > > Any pointers would be appreciated. > > > > Best regards > > > > David > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0ea09665-afe9-4fb2-a453-7dc29d98df9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
