Hi Uwe, the problem is that we’re running our jobs on a dedicated node too … unfortunately we require login access to these (in order to setup some low level socket testing stuff) and therefore can’t deploy to Nexus or push to Git (for our website).
So our build runs smoothly: Doing Tests, Integration Tests, Sonar Analysis, Website generation and then waits to get access to a node that can deploy and here the job just times-out :-/ Chris Von: Uwe Schindler <uschind...@apache.org> Datum: Donnerstag, 22. August 2019 um 17:40 An: "builds@apache.org" <builds@apache.org>, Christofer Dutz <christofer.d...@c-ware.de>, "builds@apache.org" <builds@apache.org> Betreff: Re: Fair use policy for build agents? 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
