Re: [Geotools-devel] broken builds

[Darren E. <dle...@bt...>]

I have contacted various developers from the larger java sourceforge 
projects (like JBoss and PCGen) to see what solutions they use to 
prevent broken builds.  I'll try to write up a short summary of their 
suggestions soon so they can be discussed on Mondays IRC meeting.

Not sure how many others have looked into this, but (time permitting) 
I'll try and find out some more information about CruiseControl and add 
that into the summary too.

Thanks,
Darren

Cameron Shorter wrote:
> On Thursday 22 May 2003 6:40 am, thowe wrote:
> 
>>I was reading the irc logs and noticed the issues with broken builds.
>>One thing that we have looked at is CruiseControl
>>(http://cruisecontrol.sourceforge.net).  It basically monitors the cvs
>>repository for broken builds/unit tests and reports them to a web page.
>>It is designed for ant, but perhaps there is a way to use it with maven.
>>
>>In any case, just thought I'd mention it.
> 
> 
> Thanks Tom, CruiseControl looks very promising.
>>From the docs, I couldn't work out if developers can revert back to a 
> non-broken build if the head build doesn't compile.  Eg, the latest 
> successful build could be tagged in CVS.  Do you know anything about this?
> 
> I found an email discussion about integrating maven and cruisecontrol.
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=tur...@ja...&msgNo=1551
> Seems like it is possible.
> 
> It seems that cruisecontrol requires java/jsp/tomcat.  Last time I looked, 
> sourceforge did not support a JSP engine like tomcat so in order to run 
> cruisecontrol we would require another host.  Anyone have some ideas?
>