What is it?
Test-AutoBuild is a continuous integration harness for automatically running build and test processes without the need for user interaction.
Recent news
- Friday, September 2, 2011: Release 1.2.4 of Test-AutoBuild is now available on CPAN. Read the full announcement for details.
- Mon, August 8, 2011: Release 1.2.3 of Test-AutoBuild is now available on CPAN. Read the full announcement for details.
- Sat, December 16, 2007: Release 1.2.2 of Test-AutoBuild is now available on CPAN. Read the full announcement for details.
- Sat, December 08, 2007: Release 1.2.1 of Test-AutoBuild is now available on CPAN. Read the full announcement for details.
- Sat, September 2, 2006: Release 1.0.3 of AutoBuild Applet is now available on the GNA download site
- Tue, August 22, 2006: Release 1.2.0 of Test-AutoBuild is now available on CPAN. This is the first release of the new stable release series. Read the full announcement for details.
- Sat, April 2, 2005: Release 1.0.3 of Test-AutoBuild is now available on CPAN. This is primarily a bug fix release, although it includes enhanced HTML templates and CSS styling.
- Sun, December 5, 2004: Screenshots of the GNOME panel applet for monitoring builder status
- Fri, November 5, 2004: Interview with Dennis and Daniel for the new Gna! hotspot series of articles.
Browse the news archive...
How it works
Pristine sources are checked out from a version control repository (currently has support for CVS, filesystem, Perforce, GNU Arch, Subversion). A shell script (typically provided by the application developer) is invoked to build the software and install it in a virtual root. Snapshots of the virtual root are taken before and after build to identify which files were installed. Snapshots of any designated 'package' directories are also taken to identify any RPM, Debian PKG, Tar, ZIP files which were built. Finally a set of output modules are run to generate HTML status page, copy packages and build logs to a Web / FTP server, send email notifications of build status, create ISO images.
The software is highly modularized and written in Perl to make it easily extendable to add new version control repositories, and output actions. It has no requirements around what build process an application uses (Make, autoconf, ANT, IMake), nor any requirements around the programming language used for the software.