Hi, I don't understand the background: we currently have Lucene node, so why a second one?
The ref guide stuff can easily run on other nodes. The Lucene node was added so we are able to run randomized tests all day long without blocking other projects. So as long as we have the current Lucene node, I see no reason to panic. 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. Uwe Am 28. Juni 2017 21:20:23 MESZ schrieb Steve Rowe <[email protected]>: >In an offline discussion, Cassandra Targett pointed out to me that the >INFRA issue set up to provision an additional Jenkins node for the >Lucene project <https://issues.apache.org/jira/browse/INFRA-14004> has >been closed as Won’t Fix, because: > >> Per [~gstein] we will not be provisioning any more project-specific >build nodes on our infrastructure. If they wish to provide resources, >we can connect them to our master like Cassandra, etc. > >I think that if no organization is willing to provide Jenkins hardware, >we should consider figuring out how to run Lucene/Solr tests on ASF’s >non-project-specific nodes. > >Uwe (or anybody else), do you have any thoughts about this? > >-- >Steve >www.lucidworks.com > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] -- Uwe Schindler Achterdiek 19, 28357 Bremen https://www.thetaphi.de
