The previous mass migration of projects from the old production web farms to the new VM containers provided ITAG the opportunity to institute a new centralized build and deploy process, the ITAG Release Process. Starting with the initial migration into the VM containers and continuing thereafter, all projects will be required to use the ITAG Release Process to build their applications and deploy them into the VM containers. Previously, groups had been responsible for building their own deployment modules, uploading them to Pascal, and then invoking a UNAS push script to deploy the modules. Now, ITAG will assume responsibility for both building the modules from source control and deploying them into the VM containers. While we fully expect the ITAG Release Process to evolve over time to accommodate changing needs, below are some of the key concepts and points of integration for its current implementation.