On 29/Jan/2010 10:24, Justin Mason wrote:
> On Fri, Jan 29, 2010 at 09:24, Tim Ellison wrote:
>>> I am absolutely +1 on Hudson Admin Team maintaining these boxes and giving
>>> out shell
>>> accounts to the few PMC members that really need it, and also expanding out
>>> the
>>> Hudson Admin Team
On Fri, Jan 29, 2010 at 09:24, Tim Ellison wrote:
>> What has been talked about in the past, to the Hudson admin team, is
>> restricted
>> access to Hudson Admins ONLY on the main Hudson Master box. This is going to
>> be
>> implemented real soon now and those not in the Hudson Admin Team will h
On Fri, Jan 29, 2010 at 10:24 AM, Tim Ellison wrote:
>> So, I'm certainly -1 on continuing down this track of giving shell account
>> to anyone
>> who asks for it, it's just not workable and not sensible.
>
> Agreed.
+1
> Or reducing/removing the responsibility of the "Hudson admin team" and
>
On 28/Jan/2010 12:46, Gav... wrote:
>> -Original Message-
>> From: Tim Ellison [mailto:t.p.elli...@gmail.com]
>> Sent: Thursday, 28 January 2010 2:04 AM
>> To: builds@apache.org
>> Subject: Re: Hudson access for non-PMC member
>>
>> On 27/Jan/201
Thanks for your responses, and the interesting thread. I'm asking the
Hadoop PMC to petition this list on my behalf.
Having used Hudson quite a bit recently internally to my company, it is
sometimes tricky to debug the configuration of the build without shell
access. That said, a ticket-based sy
> > that would be an option, but during our work, Mike and me only
> activated the "start new build" button in the GUI, everything else was
> and had to be done in the shell:
> > - Updating lucene's private SVN tools for the new lucene rev-based
> backwards branch (sparse checkout)
> > - Upgrading
On Jan 27, 2010, at 1:45 PM, Uwe Schindler wrote:
> Hi Grant,
>
> that would be an option, but during our work, Mike and me only activated the
> "start new build" button in the GUI, everything else was and had to be done
> in the shell:
> - Updating lucene's private SVN tools for the new lucen
> -Original Message-
> From: Tim Ellison [mailto:t.p.elli...@gmail.com]
> Sent: Thursday, 28 January 2010 2:04 AM
> To: builds@apache.org
> Subject: Re: Hudson access for non-PMC member
>
> On 27/Jan/2010 11:26, Justin Mason wrote:
> > Hi Philip --
>
m: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Thursday, January 28, 2010 1:22 PM
> To: builds@apache.org
> Subject: RE: Hudson access for non-PMC member
>
>
>
> > -Original Message-
> > From: Uwe Schindler [mailto:uschind...@apache.org]
> > Sent: Thursd
age-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Thursday, January 28, 2010 1:22 PM
> To: builds@apache.org
> Subject: RE: Hudson access for non-PMC member
>
>
>
> > -Original Message-
> > From: Uwe Schindler [mailto:uschind...@apache.org]
>
> -Original Message-
> From: Uwe Schindler [mailto:uschind...@apache.org]
> Sent: Thursday, 28 January 2010 5:21 PM
> To: builds@apache.org
> Cc: 'Uwe Schindler'; gsi...@gmail.com
> Subject: RE: Hudson access for non-PMC member
>
> > > Upgra
> > Upgrading hudson's clover version for our new coverage reports (that
> work correct with backwards branch)
>
> With the new Apache specific license you can now commit the key into
> your svn repository and therefore you might not need to do anything at
> the shell at all. That was my experie
On 28/01/10 5:45 AM, Uwe Schindler wrote:
Upgrading hudson's clover version for our new coverage reports (that work
correct with backwards branch)
With the new Apache specific license you can now commit the key into your svn
repository and therefore you might not need to do anything at the sh
> - Updating lucene's private SVN tools for the new lucene rev-based
> backwards branch (sparse checkout)
By the way, that's related to https://issues.apache.org/jira/browse/INFRA-2442,
we solved it with a private version extracted from the recent SVN stable branch
solaris build, which is done i
ermany
http://lucene.apache.org/java/docs/
> -Original Message-
> From: Grant Ingersoll [mailto:gsi...@gmail.com] On Behalf Of Grant
> Ingersoll
> Sent: Wednesday, January 27, 2010 6:38 PM
> To: builds@apache.org
> Subject: Re: Hudson access for non-PMC member
>
> Per
yeah, that's an easy way to do it. +1
On Wed, Jan 27, 2010 at 17:38, Grant Ingersoll 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
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, Ti
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
gt; From: jma...@gmail.com [mailto:jma...@gmail.com] On Behalf Of Justin
>> Mason
>> Sent: Wednesday, January 27, 2010 12:26 PM
>> To: builds@apache.org
>> Subject: Re: Hudson access for non-PMC member
>>
>> Hi Philip --
>> it's purely because the use
Hi,
On Wed, Jan 27, 2010 at 12:26 PM, Justin Mason wrote:
> 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.
+1
BR,
Jukka Zitting
/java/docs/
> -Original Message-
> From: jma...@gmail.com [mailto:jma...@gmail.com] On Behalf Of Justin
> Mason
> Sent: Wednesday, January 27, 2010 12:26 PM
> To: builds@apache.org
> Subject: Re: Hudson access for non-PMC member
>
> Hi Philip --
> it's purely
Hi Philip --
it's purely because the user accounts on the Hudson machines have
quite a lot of privileges.
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.
--j.
On Sat, Jan 23, 2010 at 01:01, Philip Ze
Hi there,
I'd like to setup a Hudson build for the AVRO subproject of Hadoop.
The current policy is to only allow such accounts for PMC/PPMC
members. Might the policy be loosened to allow accounts for
committers or an exception be made?
Thanks,
-- Philip
23 matches
Mail list logo
