These days Drupal is used on more than one million of web sites, and be sure there are many critical business applications out there which should be always available. And surely there is a slight possibility that the team working on one of these projects screw each other work from time to time during deployment directly to FTP without VCS, or just deploying broken application without following any QA procedures on Friday evening to the production server and going home. Let's add to this miscommunication in the team and lack of tests - and we get a local hell of a project manager with an angry customer calling on Saturday night.

And now let's imagine that quality of the application is checked on every commit (as all the unit tests are running on the build server and the application will never be deployed to production without all tests being green), all the developers are making code review and following the same coding standards, using the version control system, all the deployment automation is done by Phing, and the same environment is running on deployment/testing servers and developer's machines (via Vagrant) - that looks like quite the opposite of what we've seen.

During our session we'll be exploring TeamCity Continuous Integration / Continuous Deployment tool and some other tools to bring this good story to live - VCS, Phing, PHPUnit on server, deployment, Vagrant for developers, shared coding standards, IDE, code review tool, and much more.