Neverland can't be far away when you hear things like "One click install" and "Zero touch deployment". Doesn't it? The real world is tougher. Many webdevelopers spend much more time to deploy their websites. "Should I care? I have bigger problems!" Well, it depends. Perhaps it takes only two minutes to setup your server for a new Drupal-install, only half an hour to deploy a new site. But what about two hours downtime to revert a site it because it failed to deploy?

I recently investigated two popular tools which can be used for Drupal deployment: Maven and Phing.

My journey started a few month ago when I got introduced to Jenkins. Jenkins is a widely used package for continuous integration. Deployment is a part of this, but it can also be used for automatic tests, making backups, etc. It is triggered either manually, by cron or upon commit into a version control system. To me Jenkins is, beyond doubt, very suitable for Drupal deployment.