Re: Number of build prozessors on Lucene node

2015-08-20 Thread Gavin McDonald
> On 20 Aug 2015, at 10:28 am, Uwe Schindler wrote: > > Hi, > > The backlog of Lucene is generally large. That's wanted, No problem, thanks for letting me know, I’ll take that into account in the future. > because we don't trigger builds based on commits; just to always have one > build of

Re: Number of build prozessors on Lucene node

2015-08-20 Thread Uwe Schindler
Hi, The backlog of Lucene is generally large. That's wanted, because we don't trigger builds based on commits; just to always have one build of everything in the queue we do it time-based. Because of our pseudorandomized test infrastructure, the build slave should never be out of work because e

Re: Number of build prozessors on Lucene node

2015-08-20 Thread Gavin McDonald
> On 20 Aug 2015, at 9:17 am, Uwe Schindler wrote: > > Hi, > > could someone please change back the number of "build processors" for the > "lucene" Jenkins node to 1? Currently it executes always 2 Jobs in parallel. > The underlying server only has 4 cpu cores and the Lucene Job configuration

Number of build prozessors on Lucene node

2015-08-20 Thread Uwe Schindler
Hi, could someone please change back the number of "build processors" for the "lucene" Jenkins node to 1? Currently it executes always 2 Jobs in parallel. The underlying server only has 4 cpu cores and the Lucene Job configuration is done in a way that it uses all available CPU nodes, so runnin