Release Manager is a web based application that is integrated with Vahana 2.0 cloud platform. Based on the concept of GITHub, Release Manager is a code hosting and the version controlling and management application. It helps you work and manage multiple versions of the application/service or module.
Prior to the development of the Release Manager application, the Vahana platform development team had to push the code from the Production environment to the UAT (User Acceptance Testing) environment and then perform the code-fix or error fixing. After the code was fixed or changed, the developer had to merge the code back to the production environment.
This code migration from production environment to UAT environment or vice versa was tedious and time-consuming. This also tended to compromise the application up-time.
To remove these hiccups, the Vahana development team developed and launched the Release Manager application. The Release Manager application smartly allows you to cut a new child branch out of the master branch. Release Manager consists of a default master branch, which is called the â€œDevelopmentâ€ branch. All the new branches are cut out of the â€œDevelopmentâ€ branch. Therefore, you can change or fix the code in the new child branch and then merge back the child branch into the â€œDevelopmentâ€ branch.
In the Release Manager application, you can create three types of child branches as follows:
- Hotfix branch
- Deployment branch
- Backup branch
The hot-fix and deployment categories are mainly used to fix and change the application code. After the code is fixed and changed, it is synced on the VRT. The backup category is used to take the backup of the code from the master branch. You can create new child branches from the master branch up to an â€œnâ€ number of hierarchies.
This advantage gives you the leverage and freedom to work on the application code in the new branch without touching the application code in the production branch. In case, if the application code that you work on in the new child branch does not work properly, you can perform the roll-back by discarding the changes in the child branch.