Release Management

Deploying a Branch

When you initiate the deployment of a branch, the branch is automatically deployed on VRT (Vahana Run Time). On the Vahana cloud platform, VRT is a component that allows you to allocate a virtual space to the newly created environment.

To deploy a branch on VRT:

1. In the Release Manager application, click the Release Management tab, and the application displays the environment details.
2. In the Default area, click the Deploy Branch icon (), and the Deploy on <<Environment Name>> dialog box opens.

3. In the dialog box, click the Deploy New Branch list, and the application displays the list of the branches that are not deployed.
4. In the list, select the branch that you want to deploy.
5. After you select the branch, click Deploy, and the branch is successfully deployed on VRT.

Deployment Rollback

This functionality allows you to roll back the deployment of the earlier deployed branch. You can roll back the deployed branch as a result of any of the following reasons:

• Erroneous code in the deployed branch or,
• After the branch is deployed, the deployed code halts the application’s function

To deploy the rollback branch:

1. In the Release Manager application, click the Release Management tab, and the application displays the environment details.
2. In the Default area, click the Rollback Branch icon (), and the Rollback on <<Environment name>> dialog box opens.

3. The dialog box displays the following details:

Box	Description
Current Branch	This box displays the name of the currently deployed branch.
Rollback To	This box displays the name of the branch that was deployed into the environment before the current branch is deployed. After you perform the rollback, the branch that the Rollback To box displays will be redeployed.

4. On the Rollback on dialog box, click Rollback, and the application rolls back the currently deployed branch and then reverts the deployment to the last deployed branch.

Syncing Changes

This feature allows you to sync the changes of the hot-fix or the deployment branch on VRT. Syncing the changes specifies that you are imparting the changes of the deployment branch/hot-fix branch to the Vahana Run Time environment.

After you update a module or rectify the application code of the module, it is necessary to sync the updated or rectified code with the code that is running on the Vahana Run Time environment.

To sync the changes:

1. In the Release Manager application, click the Release Management tab, and the application displays the environment details.
2. In the details of the environment, click the Sync <<Environment Name>> icon (), and the currently deployed branch’s changes are synced on VRT.

Accessing Branch Details

In the Release Management module, this feature allows you to access the details of the branch. The application displays the details of the branch at the component level as follows:

• List of components that you access in the hot-fix or deployment branch
• Type of component
• Version of the component and,
• A feature to access the configuration details of the component

After you cut a branch out of the master branch to access a component, the application maintains the details of the branch on the basis of the component ID. The component ID displays the name of the component that you access in the branch.

Assume, you cut a branch to access the same component more than once. Each time you access the component, you impart changes in the component and then deploy it. In this case, the Release Management application will maintain the updated component with the incremental version number.

You can view the list of components application-wise. This feature also allows you to view the configuration details of the component in the JSON (Java Script Object Notation) format.

To access the branch details:

1. In the Release Manager application, click the Release Management tab, and the application displays the environment details.

2. In the Default area, click the horizontal arrow icon (), and the Branch Details page opens.

3. The Branch Details page displays the list of components based on the application name and type.
4. Click the tab of the application name (For example: – vConnect or vDesigner), and the application displays the list of the components that have been updated or fixed.
5. The Branch Details page displays the following details at the component level:

Branch Detail	Description
Component ID	This column displays the name of the component that you access in the hot-fix or deployment branch.
Component Type	This column displays the type of the component that you access in the hot-fix branch. The Release Manager application maintains different types of components at the system level. These component types are named variables or keywords. Based on the component that you access in the hot-fix/deployment branch, the application assigns a predefined type to the component.
Component Version	This column displays the version number of the component. The Release Manager application maintains the version of the specific updated component incrementally.
Eye Icon ()	If you click the eye icon (), the application displays the configuration details of the component in the JSON format.

Comparing Branch

This feature allows you to compare two branches. While comparing two different branches, you can view:

• The name of the component in the branch
• Version number of the component, etc.

You can use the “Compare Branches” feature to compare two different versions of the same component. To compare two different branches:

1. In the Release Management application, locate the top-right area and then click Compare Branches, and the Compare Branch page opens.

2. On the Compare Branch page:
   • Click the Branch 1 list and then select the first branch (For example: – DEVELOPMENT) to compare.
   • Click the Branch 2 list and then select the second branch (For example: – PROD_0203_1) to compare.
   • Click the Module list and then select the application (For example: – vConnect).

3. After you select the branches and the application module, click Compare, and the application displays the following details after it compares two branches:
   • Name of the component under Component ID
   • Type of component (For example:- Database)
   • Version of the component in the first branch
   • Version of the component in the second branch

4. On the Compare Branch page, click the Show only differences check box, and the application displays the list of the components that the Release Manager application maintains with multiple versions.