The Release Management System
An extensive update management of the release management system developed by elpix, is an easy way to test newly developed orders on report errors and change requests with only two mouse clicks and successfully tested releases automatically to the live system. We developed the release management system, which is closely linked to the management tasks, and MysqlAdmin and to provide maximum comfort for the customer’s projects and the documentation can be created in PDF formats using software as soda pdf online for this. All scripts and database changes can be accurately assigned to the corresponding order. This makes later analysis as simple as possible for further developments, minimum errors and good feedback.
Test Procedure / Quality Assurance
All jobs are listed with the corresponding order number, a link to the management tasks (for details), the principal, the agent, and clearly designed test links in the release management system. Only through the hard link text and the order of test links, the development of an effective testing for quality control is possible because all affected areas can be recognized and tested.
Only when all tests have been successfully completed, the management system announces the release and enables trouble-free live use. If errors are found during testing, this can easily be reported by selecting the corresponding link. Tests can be classified in the list of tasks to be done without additional costs. Each status (successful tests, failed tests, change requests, failure tests) is seen at first glance. In addition to previously-established contracts, arbitrarily far traced and upcoming changes will be considered already in advance.
Multi-Stage Development Support
The release management system allows multiple development and test environments, and live productive system. Volume jobs can be created easily on the first development without influencing other processes. Once completed, all changes (usually including database changes and scripts changes) are collected in a virtual pool to be bundled later and copied to the test environment.
While the new release is tested, it is possible to implement other orders without restrictions. If errors are found, they can be solved on the second development and replayed to the test environment. In this way, conflicts between different versions of the project are excluded.
For very urgent orders, the third development together with its own test environment are available. This enables parallel to the actual release, minor changes quickly backed by sufficient test scenarios to take into the operation.