> Why? yahoo-not-h2 is really not required since H2 is the same as all the > other H* nodes.
The yahoo-not-h2 label exists because the H2 node was misconfigured for a long time and would fail builds as a result. What label will jobs taht are currently configured to avoid H2 be migrated to? Will they be migrated automatically? > The 'docker' label references installed software and should be dropped. We > have and will continue to install docker wherever it is required. How do we determine where it's required? If I have a job that relies on docker being installed, do I just get to have it run unlabeled? On Thu, Aug 4, 2016 at 4:18 AM, Gav <gmcdon...@apache.org> wrote: > Hi All, > > Following on from my earlier mails regarding Java, Maven and Ant > consolidations, I thought > you might like a page detailing the Jenkins Labels and which nodes they > belong to. > > I've put it up here :- > > https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels > > I hope you find it useful. > > In addition I propose to remove a couple of redundant labels to make > choosing a label > easier. > > Proposal is to remove labels yahoo-not-h2, ubuntu and docker. Why? > yahoo-not-h2 is really not required since H2 is the same as all the other > H* nodes. ubuntu is a copy of Ubuntu and both are identical. > The 'docker' label references installed software and should be dropped. We > have and will continue to install docker wherever it is required. > > If no objections I'll remove these labels in ~2 weeks time on 19th August > > HTH > > Gav... (ASF Infrastructure Team) -- busbey
