www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gav <gmcdon...@apache.org>
Subject Re: Jenkins Node Labelling Documentation
Date Thu, 04 Aug 2016 21:41:09 GMT
On Fri, Aug 5, 2016 at 7:28 AM, Andrew Bayer <andrew.bayer@gmail.com> wrote:

> fwiw, I think the docker label should remain - the Rackspace dynamically
> provisioned agents, for example, are too small to really be a good option
> for most, if not all, jobs that use Docker. *shrug*
>

Too small how? Disk space, RAM, CPU, other?


>
> Alternatively, a label that distinguishes between
> the-same-in-configuration physical vs non-physical (or beefy vs non-beefy)
> agents might be worthwhile.
>

Might be worth looking into I guess. I'm trying to make things easier and
not certain that removing one label to replace with another will do that,
though it would drop the 'software naming' aspect.

At the end of the day, we are discussing a proposal, just like the recent
JDK, Maven and Ant discussions.
If consensus is that the 'docker' label is useful and we are better with it
than without, I'm fine with that.

Gav...


>
> A.
>
> On Thu, Aug 4, 2016 at 2:16 PM, Gav <gmcdonald@apache.org> wrote:
>
>> On Fri, Aug 5, 2016 at 3:14 AM, Sean Busbey <busbey@cloudera.com> wrote:
>>
>> > > 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.
>>
>>
>> Yes I know, but now its not, so is no longer needed.
>>
>>
>> > What label will
>> > jobs taht are currently configured to avoid H2 be migrated to? Will
>> > they be migrated automatically?
>> >
>>
>> Currently I'm asking that projects make the move themselves. Most jobs
>> would be fine as they have
>> multiple labels, so just need to drop the yahoo-not-h2 label to give them
>> access to H2. If, when I drop the label I
>> see jobs with it in use, I'll remove it.
>>
>>
>> >
>> > > 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?
>> >
>>
>> You are reading too much into it, what if you have a job that relies on
>> Ant, or Tomcat, or  Gradle, or ... Where are the
>> labels for those? There aren't any , and their shouldn't be, just like
>> Docker should never have been a label.
>> Docker is installed already on most nodes. If you find it missing , report
>> it.
>>
>> HTH
>>
>> Gav...
>>
>>
>> > On Thu, Aug 4, 2016 at 4:18 AM, Gav <gmcdonald@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
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message