Skip to content

Fetch the Release Update to Customer Baseline Repository

Overview

This section describe the process of fetching the Release Update to the customer baseline repository from the Release Update Studio.

Behavior of the Release Update Studio Navigator

The Release Update Studio navigator will display the two buttons; “Impact assessment” and “Apply Release Update” at the initial landing on the Release Update Studio homepage (Figure 1.1).

Figure 1.1 - Navigator of the Release Update Studio

To apply the Release Update to the customer baseline repository, the "Apply Release Update" button on the navigator needs to be clicked.

Following which the "Apply Release Update" dialog will be displayed from which the Release Update could be fetched to the baseline repository.

Trigger Apply Release Update from the Release Update Studio

Figure 1.3 - Apply Release Update dialog box

The dialog box will display a warning-type message that recommends to minimize customizations during the release update process as the environment quota is shared between both the build place and release update studio [1].

Steps to fetch the Release Update to the Customer Baseline Repository

  1. The latest Service Update for the release selected at the Request Release Update step will be shown in a label below the dropdown [2].

  2. Select the delivery tag from the Delivery Tags dropdown [3].

The Delivery Tags dropdown will list down all the approved deliveries related to the current App version in the descending order. The last approved delivery will be listed on top and will be selected by default. The delivery selected from this dropdown, will be used to create the release-update branch when fetching the release update to the Customer Baseline Repository. It is recommended to select the delivery tag related to the latest delivery deployed to the production environment of the use place. The reason for this recommendation is due to the fact that the latest approved delivery may not always be deployed to the production environment, it may still be in the testing stage in one of the non-production environments.

  1. Once both parameters are selected, the "Apply" button [4] shall be clicked to trigger the release update pipeline.

  2. If the decision is made not to proceed with the upgrade at this point, the "Cancel" button [5] shall be clicked to terminate the process.

Backend processes of fetching the Release Update to the Customer Baseline Repository

  1. The solution set will be fetched from IFS Biz and it will be stored in the relevant storage account in Azure.
  2. Central Build Services (CBS) will then migrate the Build Place related settings to its corresponding Release Update Studio.
  3. CBS will create parallel repository branches in the Azure devops project and will set branch policies to release-update branch.
  4. CBS will then pull the selected release update from the master repository to the release-update branch in the baseline repository.
  5. CBS will finally fetch the solution set from the Azure storage account, commit to the balseline repository and run the Baseline Build.
  6. This will result in creating the release-update branch in the baseline repository with the new release update and the solution set and the release-update branch in the solution repository created from an approved delivery tag.

Additional Warning Messages and Troubleshooting Steps

Upon receiving one of the warning messages listed below on the Apply Release Update Dialog (Figure 1.3), the user is required to follow the relevant troubleshooting steps mentioned under each section to move onto the latest versions of AKS cluster and/or Service Update in order to proceed with the Release Update process.

1. AKS Cluster Validation

If the AKS cluster version of a Buildplace created in the Cloud residency option is below 1.20.7, the following warning message is displayed:

  • 'Middle tier (AKS cluster) of both Build Place and Use Place should be upgraded to 1.20.7 or above to start the release update process'

If the AKS cluster version of a Buildplace created in the Remote residency option is below 1.20.7, the following warning message is displayed:

  • 'Middle tier (AKS cluster) of Build Place should be upgraded to 1.20.7 or above to start the release update process'
Troubelshooting Steps

At such an instance, it is required to contact IFS support to get the AKS cluster upgraded.

2. Service Update Validation

If the Service Update version of the customer solution repository is below 21.1.5 (21R1 track), the following warning message is displayed:

  • 'IFS Cloud 21R1 SU5 or above should be applied in both Build place and Use Place prior to start the release update process'
Troubelshooting Steps

At such an instance, a newer service update can be fetched by following the steps listed in Applying Service Updates.