You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Gav..." <ga...@16degrees.com.au> on 2010/06/29 22:54:29 UTC

All Hudson Builds Disabled

Hi,

I have just disabled all Hudson builds.

The only ones passing regularly were the docs.

The Windows build has been disabled for some time.

The other four builds used to pass ok when I fixed them a few weeks ago but
have yet again started failing regularly.

I suspect the Hudson slave environments changing due to so many people
having
access to the slaves and have carte blanche to install/change whatever they
want.

With over 185 failed build notifications to the list in the last month alone
the signal to noise ratio is far too high.

For Hudson to be useful one or two folks need to step up to be on hand to
regularly check and correct the Hudson slave environments and generally keep
on top of things.

The regular devs that do most of the committing here seem happy with the
current Buildbot setup and see no need for Hudson to join in the mix only
to be spamming the notifications list.

So, if someone wants to see Hudson enabled again, I suspect you'll need to 
argue you case well here and back it up with real promises of maintaining
Hudson and its slaves. In the meantime it will stay disabled for all builds
regarding subversion and will likely all be deleted if no resolution in the
next month or so. This will also benefit an already overloaded Hudson build
system.

Thanks

Gav... (the other one)


Re: All Hudson Builds Disabled

Posted by Greg Stein <gs...@gmail.com>.
Thanks, Gavin! Much appreciated.

Cheers,
-g

On Tue, Jun 29, 2010 at 18:54, Gav... <ga...@16degrees.com.au> wrote:
> Hi,
>
> I have just disabled all Hudson builds.
>
> The only ones passing regularly were the docs.
>
> The Windows build has been disabled for some time.
>
> The other four builds used to pass ok when I fixed them a few weeks ago but
> have yet again started failing regularly.
>
> I suspect the Hudson slave environments changing due to so many people
> having
> access to the slaves and have carte blanche to install/change whatever they
> want.
>
> With over 185 failed build notifications to the list in the last month alone
> the signal to noise ratio is far too high.
>
> For Hudson to be useful one or two folks need to step up to be on hand to
> regularly check and correct the Hudson slave environments and generally keep
> on top of things.
>
> The regular devs that do most of the committing here seem happy with the
> current Buildbot setup and see no need for Hudson to join in the mix only
> to be spamming the notifications list.
>
> So, if someone wants to see Hudson enabled again, I suspect you'll need to
> argue you case well here and back it up with real promises of maintaining
> Hudson and its slaves. In the meantime it will stay disabled for all builds
> regarding subversion and will likely all be deleted if no resolution in the
> next month or so. This will also benefit an already overloaded Hudson build
> system.
>
> Thanks
>
> Gav... (the other one)
>
>
>