Save time and test software at your convenience with scheduled builds

Most programmers have something better or more urgent to do than run the build file every few minutes. And even if everyone on the team could quickly run a full build, they might deliberately put it off because they have a deadline to meet and they're afraid someone else's changes might conflict and cause delays. A scheduled build, on the other hand, has nothing better to do than build and test everything. In this sample chapter from Pragmatic Project Automation: How to Build, Deploy, and Monitor Java Applications, learn how to take a one-step build and put on a schedule for your computer to run. Not only does scheduled automation take the one-step build process you have created and run it for you, as often as you want, without you ever having to lift a finger, but scheduled builds also identify both integration (compile time) and failing test (run time) problems quickly because they run at regular intervals. Finding problems becomes easier because you have to look only at changes that occurred in that interval, while fixing problems is easier because little problems don't have a chance to compound into bigger problems.

Title: Pragmatic Project Automation: How to Build, Deploy, and Monitor Java Applications
ISBN: 0974514039
Published: July 2004
Author: Mike Clark
Chapter: Chapter 3: Scheduled Builds
Published by Pragmatic Bookshelf