Best practice question - undo or prevent commit?

We've set up an integration environment in which we're running our automated test suite. We're currently kicking off the tests after the code is committed. The problem that presents is that if someone commits code that fails the tests (the team is new to automated tests and still getting into the habit), all the commits that follow will also fail until the problem is fixed.

My goal is to prevent 'bad' code from being committed to the repository. Is it possible to use a pre-commit hook to move the code being committed into the test environment and run the tests? Or do I need to 'undo' the commit to back out the offending code?

Thanks,
Bill
Received on 2008-02-06 13:46:21 CET