26Jun2014

Database Deployment Automation: The Whole Story

  • 1 Tags
  • 2 Comments
If a development manager tells you that it takes hours to get releases to work, and that some changes are not documented and left out, there is clearly a problem! Or, if a CTO tells you that weekly changes are deployed, just to be followed-up with multiple fix cycles, and that a crash in the integration environment is the best way to identify problems (as opposed to finding out that something works, although incorrectly, in production), then the process is probably wrong!