On Sat, Jun 16, 2012 at 1:40 AM, Ari Maniatis
<aristedes.mania...@gmail.com> wrote:
> Thanks for that idea. Unfortunately in my case I don't have enough slaves to
> set it up like that (I guess unless I create two slaves on the same physical
> machine)...
Why not get rid of the subversion hook if you don't want it to work?
Jenkins can poll for changes at reasonable rates and you can control
the scheduling. Or, put the logic of what subversion paths you want
to build instantly on every commit vs. the ones you don't into the
hook script.
--
Les Mikesell
lesmikes...@gmail.com
