Alternatively, use VM snapshots and launch the VMs you need for each job. Each one will be clean and then thrown away when the job completes. If you only have enough resources for one simultaneous build, you can continue using Throttle Concurrent Builds to maintain the restriction.
----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Mar 27 2014 03:08:32 Try using the priority sorter plugin to make the cleanup job a higher priority and it will goto the front of the queue so it will execute before any of the other queued jobs. I would probably still use the Throttle Concurrent builds plugin to ensure only one of those jobs run at the same time. Geoff On 26 Mar 2014, at 23:31, Curtis Kline <ckl...@evernote.com> wrote: I have a scenario that seems like it would be pretty common, and is maybe somewhat similar to the one David Campos posted to the list recently. b1, b2, and b3 are QA testing jobs that each rely on a “clean” VM. b4 is the job that cleans the VMs. For awhile, we had b4 set up as a downstream job from each of b1, b2, and b3. However sometimes one of the testing jobs would get queued up while another testing job was being run, and would end up running before the cleanup job. That breaks everything. Next we tried using the Throttle Concurrent builds plugin, and put all four of the above jobs into one group with a max concurrent of 1. We had the same problem as before, in that if a testing job was queued while another testing job was running, the cleanup job would run too late. Next we tried three Build Flow jobs, with the Guard - Rescue form. Each testing job would be in the Guard section, and the cleanup job in the Rescue section. We put all three of the Build Flow jobs in one group for Throttle Concurrent Builds. However we immediately found that multiple build flow jobs would run at the same time, as it seems that Build Flow jobs ignore the Throttle Concurrent Builds plugin. Any suggestions here? We just need the cleanup job to always run after a testing job, so the VMs are fresh before the next testing job runs. I am probably missing something simple. Thanks! Curtis -- 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. -- 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. -- 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.
