Re: Barracuda still doesn't compile on JDK 1.3.1

Jacob,

We actually practice Continuous Integration at my company. We have an 
internal IRC server setup, which all of engineering uses to communicate 
with each other. We also have an IRC bot attached to the server, this 
bot also listens for check ins to our cvs server. When a new file is 
checked in, it immediately starts a new build, and report a success or 
failure of the build at the end. The bot is setup so that you can 
queried about the builds, such a what part of the build it is doing, the 
last time it did a build, etc... We also have have another process that 
loads these autobuilds, and runs automated test against them. This 
process is also connected to the IRC server, and reports it's status 
there, as well as generates web based reports of it's tests.

I will look in to setting a continuous integration process. The one we 
have at work runs on a dedicated server, just because it does builds, 
and tests all day, so it chews up allot of processor time. The checkins 
for barracuda are fairly light, so it shouldn't bog down the server too 
much.

In the mean time, i will try to set up a simple daily build process that 
provides a daily downloadable set of jar files for people to try and test.

Denny

Jacob Kjome wrote:

>Hello Denny,
>
>There a number of Extreme programming based continuous integration
>tools which we could use.  These include:
>
>AntHill: http://www.urbancode.com/projects/anthill/
>
>Cruise Control: http://cruisecontrol.sourceforge.net/
>    docs for Cruise Control: http://c2.com/w4/cc/wiki.cgi?WelcomeVisitors
>
>Integration Guard: http://iguard.sourceforge.net/
>
>
>We can also register Barracuda with the Gump project (
>http://jakarta.apache.org/gump/ ) and have nightly
>builds posted under the directory:
>http://gump.covalent.net/jars/latest/
>such as
>http://gump.covalent.net/jars/latest/barracudamvc/
>
>In fact, the continuous integration stuff is something that we should
>move to, but registering the BarracudaMVC project with Gump would be
>more immediately rewarding.  I don't know all the details, but Denny,
>maybe you can look into this?
>
>
>If you are asking "what is Continuous Integration", then read this:
>http://www.martinfowler.com/articles/continuousIntegration.html
>
>Jake
>
>Tuesday, January 21, 2003, 2:49:06 PM, you wrote:
>
>  
>
>>>(*Subtle hint* - if there's anyone who wants to see this sooner rather than
>>>later, we'd love volunteers to help us figure out how best to automate daily
>>>builds and running the test suite...we have the machine, we just need
>>>someone with interest/cycles to help make this happen)
>>>
>>>      
>>>
>DC> This should be fairly easy to do with ant and cron job.
>
>DC> cron job set up to run once a day at a set time, that calls ant with a 
>DC> specific build file.
>
>DC> The build would be:
>
>DC> cvs update -d
>DC> build and test all
>DC> move to download area
>
>DC> ant can also be setup to mail interested parties on the status of each 
>DC> build.
>
>DC> I will take this as todo item.
>
>DC> Denny
>
>
>
>
>  
>