Jenkins has this problem itself on ci.jenkins.io for Jenkins core PRs taking up lots of agent resources. See https://issues.jenkins-ci.org/browse/INFRA-1633 and in particular, some of the suggested workarounds:
https://plugins.jenkins.io/PrioritySorter On Thu, 22 Aug 2019 at 10:41, Uwe Schindler <uschind...@apache.org> wrote: > > Hi, > > Lucene also "floods" with jobs, as we have a 24/7 randomized testing > infrastructure. BUT: we don't block other projects, as our jobs are bound to > two separate nodes (lucene1 and lucene2). > > I'd recommend to bind jobs that are running all the time to dedicated nodes. > Maybe have more labels and give some usage instructions. E.g., one label for > nightly builds on ubuntu vs. Another for commit or pull request builds. > > Uwe > > Am August 22, 2019 10:41:36 AM UTC schrieb Christofer Dutz > <christofer.d...@c-ware.de>: > >Hi all, > > > >we now had one problem several times, that our build is cancelled > >because it is impossible to get an “ubuntu” node for deploying > >artifacts. > >Right now I can see the Jenkins build log being flooded with Hadoop PR > >jobs. > > > >Would it be possible to enforce some sort of fair-use policy that one > >project doesn’t block all the others? > > > >Chris -- Matt Sicker <boa...@gmail.com>
