Uh, I guess I wasn't supposed to change the hudson config

[Benson Margulies <bi...@gmail.com>]

Well, so, earlier this evening hudson showed my name as SYSTEM. I
didn't think much of it. It showed me the system config department,
and I added maven 3.0.

Now, it has changed my mind, and sees that I am bimargulies, and no
longer shows me the system config department.

Net result is that the maven 3.0 installation I put in there is there,
doesn't seem to work, and I can't eliminate it.

Sorry.

Re: Uh, I guess I wasn't supposed to change the hudson config

[Niklas Gustavsson <ni...@protocol7.com>]

On Mon, Oct 25, 2010 at 1:54 PM, Benson Margulies <bi...@gmail.com> wrote:
> This is an aspect of infra that has me a bit confused. I earned my
> committer statuses on projects by <del>blackmail</del> posting
> patches. At infra, the only patching op I've seen is doc. Should I
> look for opportunities to just help on hudson when admin access is not
> required? I already help when needed with mahout and cxf.

Right, providing patches is not as easy here. But, as others have
done, you can stay around for discussions, help out on bug hunting,
report problems (just like you did now), help out with Groovy
scripting and what not.

/niklas

Re: Uh, I guess I wasn't supposed to change the hudson config

[Benson Margulies <bi...@gmail.com>]

On Mon, Oct 25, 2010 at 7:36 AM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Mon, Oct 25, 2010 at 1:30 PM, Benson Margulies <bi...@gmail.com> wrote:
>> Are you interested in another Hudson admin? I brought up hudson here
>> at the day job, and have made a few commits to Hudson myself.
>
> Yes, we're always interested in more Hudson admins. The way it works
> is like for committership, so hang around :-)

This is an aspect of infra that has me a bit confused. I earned my
committer statuses on projects by <del>blackmail</del> posting
patches. At infra, the only patching op I've seen is doc. Should I
look for opportunities to just help on hudson when admin access is not
required? I already help when needed with mahout and cxf.

>
>> Meanwhile, I'm not sure that lack of 3.0 support explains anything,
>> since using the seemingly supported 3.0 beta I got the same error.
>>
>> For a freestyle stopgap, should I just unpack 3.0 in my personal
>> directory on unbuntu1?
>
> The best thing is to request an installation as described here:
> http://wiki.apache.org/general/Hudson#What_should_I_do_with_the_build_and_test_tools_that_my_project_needs.3F
>
> In this case, we should set up a general Maven 3.0 installation
> (upgrading the currently provided beta), feel free to open an infra
> ticket so it doesn't fall between the cracks.

Can do.

>
> /niklas
>

Re: Uh, I guess I wasn't supposed to change the hudson config

[Niklas Gustavsson <ni...@protocol7.com>]

On Mon, Oct 25, 2010 at 1:30 PM, Benson Margulies <bi...@gmail.com> wrote:
> Are you interested in another Hudson admin? I brought up hudson here
> at the day job, and have made a few commits to Hudson myself.

Yes, we're always interested in more Hudson admins. The way it works
is like for committership, so hang around :-)

> Meanwhile, I'm not sure that lack of 3.0 support explains anything,
> since using the seemingly supported 3.0 beta I got the same error.
>
> For a freestyle stopgap, should I just unpack 3.0 in my personal
> directory on unbuntu1?

The best thing is to request an installation as described here:
http://wiki.apache.org/general/Hudson#What_should_I_do_with_the_build_and_test_tools_that_my_project_needs.3F

In this case, we should set up a general Maven 3.0 installation
(upgrading the currently provided beta), feel free to open an infra
ticket so it doesn't fall between the cracks.

/niklas

Re: Uh, I guess I wasn't supposed to change the hudson config

[Benson Margulies <bi...@gmail.com>]

Niklas,

Are you interested in another Hudson admin? I brought up hudson here
at the day job, and have made a few commits to Hudson myself.

Meanwhile, I'm not sure that lack of 3.0 support explains anything,
since using the seemingly supported 3.0 beta I got the same error.

For a freestyle stopgap, should I just unpack 3.0 in my personal
directory on unbuntu1?

--benson

Re: Uh, I guess I wasn't supposed to change the hudson config

[Niklas Gustavsson <ni...@protocol7.com>]

On Mon, Oct 25, 2010 at 12:28 AM, Benson Margulies
<bi...@gmail.com> wrote:
> Well, so, earlier this evening hudson showed my name as SYSTEM. I
> didn't think much of it. It showed me the system config department,
> and I added maven 3.0.

It's a bug in Hudson which has been reported to the Hudson devs (but
there doesn't seem to be much action on it)

> Net result is that the maven 3.0 installation I put in there is there,
> doesn't seem to work, and I can't eliminate it.

Right, as far as I know, Maven 3 is not yet supported by Hudson, so if
you need to use it, you need to run a free style build.

I've removed the Maven installation you added.

/niklas