Today my task was to setup the autobuild environment for a project I’m working on. After speaking to some colleagues about setting up ‘cruisecontrol’ I decided to google around a bit. It paid off!
The maven2 project features a full blown integration server in the likes of Continuum a integration server for Maven2, Maven1, Ant and plain old shell scripts!
After reading the installation instructions I downloaded the installation bundle on one of the Suse development servers and ran the startup script. Nothing…
Starting the server in ‘console’ mode revealed the problem: port 8080 was already taken! The, for once, useful documentation on the maven site explained how to configure Jetty to run on another port. done.
Pointing my browser to the installation, now running on 9090 a nice wizard popped up which helped me configuring Continuum.
After the installation was finished I tried uploading my pom and getting it to build. But… first….. I had configure the source code management part of my project file.
The project was already checked in in CVS, but I didn’t bother to configure it in the project file:
After adding this line, I pressed ‘build’ et voila! The autobuild worked!
When playing around a bit, we discovered we couldn’t get the autobuilds to accept SVN managed projects from a HTTPS server, might have a look at that in a short while… apart from that Continuum rocks! The MSN-notifier worked right out of the box, and email configuration wasn’t to difficult either… didn’t try the IRC and Jabber notifications yet.
Build cycles are internally scheduled using quartz and configuration is quite similar to the crontab, but now from a web-interface. It is also possible to have multiple schedulers, and assign different schedulers for different projects!
If I discover other interesting features of Continuum, I’ll let you know!
Great!
0 Responses to “Continuum”
Please Wait
Leave a Reply