> There has been discussion of automatically testing patches on JIRA issues (SOLR-10912). As far as I’m concerned, we won’t be able to consider that until/unless we have more Jenkins bandwidth.
I don't think we need to dedicate resources to Yetus patch testing. It runs on generic ASF nodes. On Wed, Jun 28, 2017 at 4:03 PM, Steve Rowe <sar...@gmail.com> wrote: > Hi Uwe, > > > On Jun 28, 2017, at 4:10 PM, Uwe Schindler <u...@thetaphi.de> wrote: > > > > I don't understand the background: we currently have Lucene node, so why > a second one? > > Our randomized testing regime means the more bandwidth, the better. Are > you seriously arguing against increasing testing frequency? > > There has been discussion of automatically testing patches on JIRA issues > (SOLR-10912). As far as I’m concerned, we won’t be able to consider that > until/unless we have more Jenkins bandwidth. > > Also, it would be nice to be able to run regular performance benchmarks, > but without more bandwidth, that would not be a prudent use of the currenly > limited resources. > > > BTW, the Policeman server now has new hardware like NVME RAID drives and > faster CPU. See it as donation to the project. It is not linked to ASF > because of custom build behavior regarding JDK randomization, that's not > possible to setup at ASF. > > Thanks Uwe for running your Jenkins. It’s great to have regular testing > on all the platforms you support. > > -- > Steve > www.lucidworks.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
