Plan, Execute and Track Application updates through every stage of the lifecycle
At MidVision, we use the term Release Management to describe the flow of Application, Middleware and Database related changes as they flow from the Developers who initially produce them, through the environments ultimately to production.
Software Release Challenges
The release process in most established enterprises requires a lot of manual co-ordination, often performed using spreadsheets and maintained by release managers. Release Managers usually attempt to co-ordinate with the technical teams the applications and versions to be deployed to each of the many environments on a path to production.
This process is inefficient and resource intensive, lacks visability and transparency – and is prone to human error. It does not adequately track conflicts, delays nor does it effectively highlight errors in the software release process.
RapidDeploy allows you to plan, execute and track a release through every stage of the lifecycle model. The application deployment lifecycle is mapped within the tooling – increasing the speed, reliability and transparency of the software release process.
Complex multi component applications can be moved from one environment to the next as a single unit of work, re-using a consistent set of automation and orchestration procedures in every environment the application is deployed to.
Self service is promoted through the life cycle – developers, Tester, Operations or any other team members are each able to deploy, request, approve or track releases through the lifecycle.
What does MidVision offer?
Human and Automated Quality Gates
Quality Gates are an important part of the application lifecycle. The reason organisations have many development and test environments is that they are required to pass some validation inorder to progress onto the next target on the applications ‘Path to Production’.
These validations can be in the form of a human approvals, such as individuals or group members, given approvals to deploy an application to the next environemnt. Alternatively, they may be Automated quality gates, such as invoking an automated test suite. If expected results are within a certain range then approve to be promoted to the next environment.
Scheduling, identify contentions and blackout periods
Schedule deployments to occur at specific times, identify any contentions in the release process, queue and manage multiple releases to the same targets if required. Deployment windows can be defined as well as blackout periods when deployments are not permitted.