I generate our Hudson configuration from data in CVS - in a project built by
Hudson. This means the configuration is under version control.
See http://buildmeister.blogspot.com/2009/06/configuration-of-hudson.html

Ideally, the project should be built by a special builder with this behavior:

1. Prepare Hudson for shutdown
2. Wait for all running jobs to complete
3. Build the project
4. Resume if the project failed, otherwise restart the Hudson Service.

The project (if builds to completion) will copy the new configuration tree on
top of Hudson's active configuration tree.

It would be extra cool if the configuration validity could be verified before it
was activated. Maybe the builder should pick up the new configuration from the
project dist folder - then verify it before activating it.