Automated build process The major impetus for implementing and maintaining an automated build process is to provide a simple and convenient method for developers to perform builds for development, test, and production environments. The main problems you might run into when you do not have an automated process are as follows: _ Failures on your test or production environment because the code was not packaged correctly. _ The wrong code was deployed causing the application to fail. _ The development team, testers, and even customers have to wait to get the code out to a test, staging, or production environment because the only person who has control over these areas is unavailable. _ You cannot reproduce a problem on production because you do not know what version of files are in production at the moment. The time spent developing an automated build script will pay for itself over time. After you have an automatic build process in place, you can virtually eliminate failures due to improper deployment and packaging, considerably reduce the
This is the end of the preview. Sign up
access the rest of the document.
This note was uploaded on 03/26/2012 for the course ITC 020 taught by Professor Abcd during the Spring '12 term at Andrew Jackson.