The development practice of Continuous Integration has become a de facto standard for development teams trying to become more Agile. The benefits of Continuous Integration are extremely impactful and much has been written on the topic. By automating the building and testing of software, a development team creates a repeatable and consistent build process. By extending this process into the concept of continuous provisioning, a development team extends the same type of repeatability and consistency to application deployments. If the up-front cost of automating the build and deployment of an application is nothing compared to the time and cost savings to be incurred, then why does automation stop there? Why do most development teams still need to wait for the underlying infrastructure to be provisioned? Why do developers and operations teams manually install and configure middleware (application servers, databases, etc)?
This article will illustrate to teams how continuous provisioning can be leveraged during development.