How does ControlTier speed up and improve the quality of an app lifecycle that spans DEV, QA, PROD, etc?
Moving change from development through QA and on into production is generally a time consuming, error-prone, and all around painful experience. All kinds of new artifacts and related knowledge must be passed for both major and minor releases including: • versioning and dependencies across multiple packages • data and database schema updates • node names, file locations, and permissions (often different in each environment) • configuration files and settings • control scripts and command line syntax • sequencing of startup across components It’s difficult enough to get these details right if you are the primary developer of the service, but it’s almost impossible to get all of this knowledge handed off to QA and Production staff in a way that is both efficient and reliable. To further compound the problem, it’s not uncommon for each team to have their own tools and processes to accomplish the changes in their respective environments. When you add up all of the miscommunication, manual e