Sure thing, sounds reasonable to me.

Thanks Gavin.

Patrick

On Sat, Aug 6, 2016 at 7:28 PM, Gav <gmcdon...@apache.org> wrote:

> Hi,
>
> On Sun, Aug 7, 2016 at 11:08 AM, Patrick Hunt <ph...@apache.org> wrote:
>
>> Hi Gavin. afaik we had those labels in order to run our "hadoop qa bot"
>> process. Looks like four jobs currently have that label:
>>
>> https://builds.apache.org/label/Zookeeper/
>>
>> as long as we can continue to run the "hadoop qa bot" on any other (non
>> H* nodes) I believe we don't have any other reason to require that label.
>> Perhaps clover?
>>
>> Can you confirm that the non H* hosts are configured similarly at this
>> point?
>>
>
> They should all be the same now yes. However in dropping the ZooKeeper
> label the intention was to move you to the Hadoop label, meaning you stay
> on the H* nodes anyway - you just end up on more of them.  Make sense?
>
> Gav...
>
>
>>
>> Patrick
>>
>>
>> On Sat, Aug 6, 2016 at 4:56 PM, Gav <gmcdon...@apache.org> wrote:
>>
>>> Hello All!
>>>
>>> Please take a look at:-
>>>
>>> https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels
>>>
>>> I do not see a need any longer for the project specific labels.
>>>
>>>
>>> I think we can drop all of these:-
>>>
>>>
>>> HDFS, MapReduce, Pig, Falcon, Tez, ZooKeeper.
>>>
>>> (yahoo-not-h2 and ubuntu labels are already being discussed to drop)
>>>
>>>
>>> Unless I hear objections within the next 5 days, I'll go ahead and move
>>> everyone
>>> using those to the Hadoop label.
>>>
>>> I am not subbed to your list , replies to builds@ cc: to me please.
>>>
>>> For those of you that configure jenkins and/or buildbot builds and are
>>> not
>>> subbed to the builds@ list, I encourage you to do so.
>>>
>>> Thanks
>>>
>>> Gav...
>>>
>>
>>
>

Reply via email to