Hi Andrew & Cameleers, our builds take really long time (we have a lot of modules/tests), it's not uncommon for a full build/test to run for ~5 hours.
I think the best course would be to never run tests in two jobs or only run them once per day. I was experimenting with throttle[1] and ere is what I've came up with[2] (I've used the `Hive` category that exists on builds.apache.org). I seem to be missing something, as the shell in the Test stage still gets executed in parallel when I trigger two jobs. What I think would be best for us is to have the Test stage only in single job execution and other, parallel, executions would skip over it. This way we'd never take up 4h of agent's time concurrently. Or we could have it only runs once per day, but I'm not sure on how to do that with a single declarative pipeline. Anyone has a better idea/solution? zoran [1] https://jenkins.io/doc/pipeline/steps/throttle-concurrents/ [2] https://gist.github.com/zregvart/a42b0dcb58e2280983a128d845acfbc0 -- Zoran Regvart
