Probably it would also be fair to not parallelise all modules (i.e. reserve only handful number of slots instead of almost all available). Currently we trigger 35 builds at the same time: https://github.com/apache/jackrabbit-oak/blob/6c04951be723c4574d3a7c1bcc4ec04e9f9e7dd0/Jenkinsfile#L23 <https://github.com/apache/jackrabbit-oak/blob/6c04951be723c4574d3a7c1bcc4ec04e9f9e7dd0/Jenkinsfile#L23> while ASF Jenkins has only about the same amount of slots. I think we should block at most a handful of nodes in parallel (although this may lead to slightly slower build times).
Konrad > On 14. Nov 2022, at 16:29, Konrad Windszus <[email protected]> wrote: > > Seems this is pretty easy: https://stackoverflow.com/a/70375236 > <https://stackoverflow.com/a/70375236> > Can you come up with a PR? > Thanks, > Konrad > >> On 14. Nov 2022, at 16:16, Marcel Reutegger <[email protected]> >> wrote: >> >> Hi, >> >> On 11.11.22, 15:11, "Robert Munteanu" <[email protected]> wrote: >>> I think it would be worthile to check if the build can be optimised, >>> otherwise Oak builds are blocking many execution slots of the Jenkins >>> ASF instance. >> >> I did notice one thing. Our PRs may schedule a build each time commits >> are pushed to the branch. Is there a way to cancel an already running >> build when there are new changes coming in from a PR? >> >> Regards >> Marcel >
