: 26 March 2014 23:31
To: jenkinsci-users@googlegroups.com
Subject: Downstream cleanup job
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
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.
- Origin
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.
Ge
On 27.03.2014, at 00:31, Curtis Kline wrote:
> 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.
Make the cleanup a regular part of the jobs b1-b3.
If you n
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
