Skip to content

Process after Applying Release Update to Baseline Repository

Overview

Once the Apply Release Update to Baseline Repository step is completed, the customer may choose a path based on the customization that exist in their Customer Solution repository. This section guides you on which path to select to move forward with the Release Update process.

Scenario 01: Taking a Release Update While Customizations Exist in the Repository

If your Release Update Summary table is as follows (Figure 4.1) after the Release Update is applied to the baseline repository, it is because there are additional files other than the mandatory files* existing in the customer solution repository of the release-update branch.

Note

  • Mandatory files are version.txt, solutionset.yaml, and translationusage.json.
Figure 4.1 - Release Update Summary Table When Customization Exist (RU on 22R2 or Later Version)

These users are identified as customers who are implementing customizations or configurations within their Build Place. Hence, they will be taken through the full flow of the Release Update process.

Further, if the RU version is on a version below 22R2, you may see the summary table as shown in Figure 4.2 and you will also need to go through the full flow of taking a Release Update.

before-22r2-apply-ru-in-baseline-complete
Figure 4.2 - Release Update Summary Table When Customization Exist (RU on a Version Below 22R2)

Customers that fall under the above mentioned categories can follow the Taking a Release Update While Customizations Exist in the Repository section of the documentation.

Scenario 02: Taking a Release Update While Customizations Do Not Exist in the Repository (Applicable for 22R2 and Beyond)

If the customer solution repository of the release-update branch consists of only the mandatory files, these customers are identified as customers who are not implementing any customizations or configurations within their Build Place. Hence, they will be taken through the shorter path of the Release Update process (Figure 4.3). Note that this is only applicable for core-cust separated Build Places (i.e. Release Update version you are planning to take is 22R2 or higher).

Such customers can follow the Taking a Release Update While Customizations Do Not Exist in the Repository section of the documentation.

Figure 4.3 - Release Update Summary Table When No Customization Exist