Hudson nodes + labels
Here's a proposal for tweaking the Hudson nodes usage. It's not much of a change and hopefully reflects what is happening already, project specific resources run tied project jobs, and general purpose nodes are labeled with OS identifiers for those that care. Comments welcome. Label: Master : tied jobs only Label: Lucene Lucene : tied jobs only (for Lucene project) Label: Solaris10 : any job Label: Ubuntu Minerva : any job Vesta : any job Label: Hadoop hadoop1-8 : tied jobs only (for Hadoop project) Label: Win2008 : any job Jobs should be encouraged to specify node requirements as generally as possible, i.e. 'any node' before a node type (via label) before a specific node (via name). We then try to reduce load on Master by generalizing jobs away from the master node unless they need to run there, e.g for config purposes. AIUI is requested by INFRA-2360 is awaiting new disks for nyx, Gavin is looking at alternatives now. Regards, Tim
Re: Hudson nodes + labels
Hi, On Fri, Dec 4, 2009 at 9:41 AM, Tim Ellison wrote: > Here's a proposal for tweaking the Hudson nodes usage. It's not much of > a change and hopefully reflects what is happening already, project > specific resources run tied project jobs, and general purpose nodes are > labeled with OS identifiers for those that care. Comments welcome. +1 Sounds good. It would be good if we documented better what tools (and versions) are available on all nodes and on all nodes with a given label. For example the PDFBox site build requires a recent version of Forrest, which I've installed on Minerva and the Hudson master. I should make that available (and document it's availability) on all nodes where PDFBox may get built. BR, Jukka Zitting
Re: Hudson nodes + labels
On Fri, Dec 4, 2009 at 9:41 AM, Tim Ellison wrote: > Here's a proposal for tweaking the Hudson nodes usage. It's not much of > a change and hopefully reflects what is happening already, project > specific resources run tied project jobs, and general purpose nodes are > labeled with OS identifiers for those that care. Comments welcome. Big +1 /niklas
Re: Hudson nodes + labels
On 04/Dec/2009 08:47, Jukka Zitting wrote: > Hi, > > On Fri, Dec 4, 2009 at 9:41 AM, Tim Ellison wrote: >> Here's a proposal for tweaking the Hudson nodes usage. It's not much of >> a change and hopefully reflects what is happening already, project >> specific resources run tied project jobs, and general purpose nodes are >> labeled with OS identifiers for those that care. Comments welcome. > > +1 Sounds good. > > It would be good if we documented better what tools (and versions) are > available on all nodes and on all nodes with a given label. For > example the PDFBox site build requires a recent version of Forrest, > which I've installed on Minerva and the Hudson master. I should make > that available (and document it's availability) on all nodes where > PDFBox may get built. Yep. Unless you have a better idea I'll create pages on the general wiki, and link to them from the Hudson page [1]. [1] http://wiki.apache.org/general/Hudson Regards, Tim
Re: Hudson nodes + labels
On Friday, December 4, 2009, Tim Ellison wrote: > On 04/Dec/2009 08:47, Jukka Zitting wrote: >> Hi, >> >> On Fri, Dec 4, 2009 at 9:41 AM, Tim Ellison wrote: >>> Here's a proposal for tweaking the Hudson nodes usage. It's not much of >>> a change and hopefully reflects what is happening already, project >>> specific resources run tied project jobs, and general purpose nodes are >>> labeled with OS identifiers for those that care. Comments welcome. >> >> +1 Sounds good. >> >> It would be good if we documented better what tools (and versions) are >> available on all nodes and on all nodes with a given label. For >> example the PDFBox site build requires a recent version of Forrest, >> which I've installed on Minerva and the Hudson master. I should make >> that available (and document it's availability) on all nodes where >> PDFBox may get built. > > Yep. Unless you have a better idea I'll create pages on the general > wiki, and link to them from the Hudson page [1]. +1. Also it may be possible to define your own label like 'has-forrest', add that to the relevant hosts, and require that in yr builds. > > [1] http://wiki.apache.org/general/Hudson > > Regards, > Tim > > -- --j.
Re: Hudson nodes + labels
+1. On Dec 4, 2009, at 12:41 AM, Tim Ellison wrote: Here's a proposal for tweaking the Hudson nodes usage. It's not much of a change and hopefully reflects what is happening already, project specific resources run tied project jobs, and general purpose nodes are labeled with OS identifiers for those that care. Comments welcome. Label: Master : tied jobs only Label: Lucene Lucene : tied jobs only (for Lucene project) Label: Solaris10 : any job Label: Ubuntu Minerva : any job Vesta : any job Label: Hadoop hadoop1-8 : tied jobs only (for Hadoop project) Label: Win2008 : any job Jobs should be encouraged to specify node requirements as generally as possible, i.e. 'any node' before a node type (via label) before a specific node (via name). We then try to reduce load on Master by generalizing jobs away from the master node unless they need to run there, e.g for config purposes. AIUI is requested by INFRA-2360 is awaiting new disks for nyx, Gavin is looking at alternatives now. Regards, Tim
