forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: Could Forrest use Hudson?
Date Wed, 27 Aug 2008 08:02:39 GMT
Gavin wrote:
> Just wondering, 
> Would Hudson [1] and its variety of Plugins [2] be of any use to Forrest?
> If so then we would need to decide where to install it, choices are :-
> 1.
> 2.
> 3. or my server [3].
> I do not favour the first choice Hudson.zones at the moment as it is far too
> overloaded as it is. That may be revisited if it moves to a better server.

I prefer this option 1. Listening to ASF Infra lists, the
group of Hudson people seem to be sorting it out.

Been watching it today and it seems to be getting through
the queue okay.

ASF Infrastructure do not manage such services. They expect
the projects who use it to do that. So there would need to
be at least one person from Forrest participating with the
Hudson group. I will not be.

> I think forrest.zones would be a good choice, performance related I think we
> should be ok as we don't do that much on it, however performance also
> depends on other zones loads at the time.

I don't like this option. We the Forrest PMC need to manage it.
A shared Hudson makes more sense to me.

We would be better to put effort into managing our existing
Forrest-related stuff.

> If folks don't want 1 or 2 then I don't mind hosting it on my server. I'm
> pretty sure it can handle it without any problems.

The problem is that if you go away, then we are left
in the lurch.

> I have another project
> running on it currently and has been doing great, and devs are benefiting
> greatly from some plugins such as PMD, FindBugs, Violations etc. Take a look
> at the current project and click through to see some of the above plugins
> reports and trends (e.g [4]). A benefit of this choice also is of course
> some of the work is done in that we have a working installation already.
> So, thoughts, useful or not, if so , where ?

We already use Apache Gump for some things. In the past
it helped us a lot with continuous integration when it
built Cocoon-2.2 trunk and then us. Then we lost out when
Cocoon-2.2 went to Maven. Now that Gump can build Maven-based
projects, Cocoon is back but we are too far behind to use it.

Perhaps Gump can still help us if we go to Cocoon-2.1 branch.

Anyway, Hudson does different things and would probably
be useful too.

I think that we would benefit from such CI tools.
However, i don't have time to help with Hudson.


> Gav...
> [1] - 
> [2] - 
> [3] -
> [4] -

View raw message