Perl and Daily Builds

It sounds like many folks see substantial benefits, especially on teams.

So, I was wondering what a nightly build process might look like to a team using Perl.
Here are a few thoughts:

Do a complete checkout from cvs of html pages and scripts

Run a link checker for static html pages

Run all unit tests

Run all regression tests

Any errors break the build

tar / gzip everything, and save with a datestamp / build number

The nightly build then becomes the tool for syncing the staging and production servers, rather than using cvs update to sync the servers. The benefit of this is that you can cvs commit files that are not 100% functional / stable, and not worry that they will be released into production on a nightly update, while still maintaining a record of each night's build and smoke test.

Is anyone working on a Perl project and doing nightly builds? Do you find it useful?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Cool stuff. What I'm trying to sort out for myself is if there are additional benefits to be found from doing a build on a nightly basis. That is, doing a cvs checkout into a fresh directory, firing up an Apache process which points to that directory, running the automated tests, then (assuming everything passes) tar'ing up the directory and storing it away.

The tests that you are doing seem to capture a lot of the benefits of a nightly build: