You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Steve Rowe <sa...@gmail.com> on 2017/07/11 05:06:01 UTC

Re: Increasing ASF Jenkins bandwidth

Well that’s bizarre - as Pono mentioned on thread “New Jenkins build node”, we now have a second Jenkins node named “lucene2".  Both the “lucene" and the “lucene2" node are under the “lucene” label, which should cause the jobs to be distributed across the two nodes without any configuration changes, since all our jobs are tied to the “lucene” label.

Many Jenkins jobs have failed since “lucene2" came online an hour ago, because “ant ivy-bootstrap” hasn’t been run on “lucene2”.

On Jun 28, 2017, at 5:47 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> The second question was, if there is anything against using the other nodes for running Lucene tests? My answer to that is:
> […]
> - You can easily run Lucene jobs on other nodes, just not with a 24/7 schedule 😊 The only thing you have to do is: (a) invoke "ant iv-bootstrap" once per node (see the manual job on our node to trigger this);

I manually started the "Lucene-Ivy-Bootstrap” job after reconfiguring it to run on the “lucene2” node.  Hopefully that will allow jobs to succeed there.

> (b) ideally place a lucene.build.properties file on the node's home directory with node-specific config. Problem is that Lucene's automatic CPU assignment can be tuned for jenkins nodes (you can use all cpus, but on the other hand if a node has multiple executors, go down). As this is job-unspecific, it's better to deploy that as config file on the node's home directy. The lucene node has a lucene.build.properties, the same for Policeman Jenkins.

I copied the contents of /home/jenkins/lucene.build.properties from the “lucene” node into a shell script build task on the “Lucene-Ivy-Bootstrap” job, then ran the job again to populate the same file on the “lucene2” node.

So the “lucene2” node (and jobs running on it) should be good now.

--
Steve
www.lucidworks.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: Increasing ASF Jenkins bandwidth

Posted by Steve Rowe <sa...@gmail.com>.
> On Jul 11, 2017, at 3:41 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> 
> Thanks Steve!
> 
> How came that we got a second machine? Is it a VM or is it some other (sponsored one)?

It is a VM.  See <https://issues.apache.org/jira/browse/INFRA-14004>.

INFRA-14004 was closed as “Won’t Fix” a month ago, and then suddenly yesterday the request on that issue was honored.

I don’t understand why (hence my comment about it being bizarre), but we were maybe grandfathered out of Greg Stein’s kiboshing of new project-specific VMs (see <https://issues.apache.org/jira/browse/INFRA-14004?focusedCommentId=16033963&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16033963>).

--
Steve
www.lucidworks.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


RE: Increasing ASF Jenkins bandwidth

Posted by Uwe Schindler <uw...@thetaphi.de>.
Thanks Steve!

How came that we got a second machine? Is it a VM or is it some other (sponsored one)?

Uwe

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de

> -----Original Message-----
> From: Steve Rowe [mailto:sarowe@gmail.com]
> Sent: Tuesday, July 11, 2017 7:06 AM
> To: dev@lucene.apache.org
> Subject: Re: Increasing ASF Jenkins bandwidth
> 
> Well that’s bizarre - as Pono mentioned on thread “New Jenkins build node”,
> we now have a second Jenkins node named “lucene2".  Both the “lucene"
> and the “lucene2" node are under the “lucene” label, which should cause the
> jobs to be distributed across the two nodes without any configuration
> changes, since all our jobs are tied to the “lucene” label.
> 
> Many Jenkins jobs have failed since “lucene2" came online an hour ago,
> because “ant ivy-bootstrap” hasn’t been run on “lucene2”.
> 
> On Jun 28, 2017, at 5:47 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> > The second question was, if there is anything against using the other nodes
> for running Lucene tests? My answer to that is:
> > […]
> > - You can easily run Lucene jobs on other nodes, just not with a 24/7
> schedule 😊 The only thing you have to do is: (a) invoke "ant iv-bootstrap"
> once per node (see the manual job on our node to trigger this);
> 
> I manually started the "Lucene-Ivy-Bootstrap” job after reconfiguring it to run
> on the “lucene2” node.  Hopefully that will allow jobs to succeed there.
> 
> > (b) ideally place a lucene.build.properties file on the node's home directory
> with node-specific config. Problem is that Lucene's automatic CPU
> assignment can be tuned for jenkins nodes (you can use all cpus, but on the
> other hand if a node has multiple executors, go down). As this is job-
> unspecific, it's better to deploy that as config file on the node's home directy.
> The lucene node has a lucene.build.properties, the same for Policeman
> Jenkins.
> 
> I copied the contents of /home/jenkins/lucene.build.properties from the
> “lucene” node into a shell script build task on the “Lucene-Ivy-Bootstrap” job,
> then ran the job again to populate the same file on the “lucene2” node.
> 
> So the “lucene2” node (and jobs running on it) should be good now.
> 
> --
> Steve
> www.lucidworks.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org