UrbanCode

How to apply an Emergency Fix to a Release using IBM UrbanCode Release

By Randall Langehennig posted Wed September 01, 2021 05:50 PM

  

How to apply an Emergency Fix to a Release using UrbanCode Release

Author: Randy Langehennig

Date: 05/25/2021

Overview

In IBM UrbanCode Release, when it comes time to perform the deployment against a target environment, what is the procedure to follow should something fail and a rollback or another deployment is required to complete the work?   In this document, we show the best practice method of approaching this using IBM UrbanCode Release.

Steps to Follow

If something happens during the major monthly release and a fix is required to one or more of the applications (MuleSoft, Mainframe, OpenShift as example), one can follow these steps:

1) Setup a deployment plan which includes the steps required to fix the issue.  In the meeting today, I created a "MuleSoft-Example" plan as shown below:


I think it may be best to use a naming standard with a prefix of the release to help make it clear.   For example:

I chose to Copy From "Sample Release - Default Plan" but you may have something setup for this that is a better starting point in the future.  

2) After you have created the Deployment Plan (e.g. R2021-05-Emergency-Fix", you can then execute this plan to apply your fix to the release.   Click on the "Deployments" sub-tab as shown below:

3) Click the "Add New" button (as shown above)

4) Select your release, your phase (in this case PROD), and your deployment plan we just added for the emergency fix as shown below:

5) Click the Save button

6) Your deployment is scheduled and shown in the list as shown below:

7) To initiate the emergency fix, click on the execution date link for the item (as shown above)

8) Click on the "Applications & Versions" sub-tab and select a version (or versions) you want to deploy for a given application (e.g. eSignature or more):


9) Click Save and your version appears in the list as shown below:

10) In the "Deployment Execution" sub-tab, add your automated task to deploy the eSignature application as shown below:

11) Click the "Start Deployment" button (as shown above)

12) The deployment will execute and should complete as shown below:

Using this process is helpful for situations where you need to rollback a failed deployment as part of your release process or deploy a fix to the application.   This completes this blog post and I hope this was helpful for our IBM UrbanCode Release community.
0 comments
12 views

Permalink