www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Mason ...@jmason.org>
Subject Re: Hudson access for non-PMC member
Date Wed, 27 Jan 2010 17:44:24 GMT
yeah, that's an easy way to do it.  +1

On Wed, Jan 27, 2010 at 17:38, Grant Ingersoll <gsingers@apache.org> wrote:
> Perhaps there is an in-between here, too.  Can't we give access to Hudson itself w/o
giving access to the machine?  That way, Uwe could run and configure the jobs (which is the
most common task) w/o necessarily needing to deal w/ the machine level stuff.
>
> -Grant
>
> On Jan 27, 2010, at 11:04 AM, Tim Ellison wrote:
>
>> On 27/Jan/2010 11:26, Justin Mason wrote:
>>> Hi Philip --
>>> it's purely because the user accounts on the Hudson machines have
>>> quite a lot of privileges.
>>
>> Anything much more significant than people's privileges via their
>> people.a.o accounts?
>>
>>> Personally I'm open to the idea of making an exception if the AVRO PMC
>>> call for it, and assuming none of the other Hudson admins are against
>>> it.
>>
>> Not against it, but if there is a flood of new account requests from
>> committers I'd like to examine whether we can roll those machines into
>> the existing infra routines.
>>
>> Regards,
>> Tim
>
>
>



-- 
--j.

Mime
View raw message