Apply Release Update to Solution and Sanity Build¶

Overview¶

Once the Release Update is applied to the baseline repository, if the customer Build Place is a "Build Place Without Customizations", the next step would be to apply the Release Update to the Customer Solution repository and run a sanity build. When the operation is triggered, the Release Update available in the customer baseline repository will be fetched and applied to the Customer Solution repository and a sanity build will be run to ensure there are no build errors.

How to Identify a Build Place with No Customizations?¶

Once the Apply Release Update to Baseline step is completed, 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.

Note

Mandatory files are version.txt, solutionset.yaml, and translationusage.json.

What is Advanced Release Update?¶

Customers who are identified as those who do not have customizations existing in their repositories, are given the option to switch to a view with more options. This view will be similar to a Release Studio when Taking a Release Update to a Build Place With Customizations.

You can switch to this view by clicking on the 'Advanced Release Update' button (Figure 1.1).


Figure 1.1 - Advanced Release Update Button

By switching to this view, you will be able to:

Send a fix for an already deployed delivery
Order multiple deliveries from the Release Update Studio
Order environments from the Release Update Studio

How to Perform Advanced Release Update Operation?¶

If you are required to perform any of the operations mentioned above, you can switch to the Advanced Release Update flow by clicking on the 'Advanced Release Update' button. This will provide you with all the options that a "Build Place With Customizations" would have.

Note

If TDM is disabled, the 'Advanced Release Update' option is available until the 'Complete Release Update' step is completed.
If TDM is enabled, the 'Advanced Release Update' option is available until the 'Test Data Update' step is completed.
Once you switch to the advanced view of the Release Update process, you are unable to switch back to the previous state.

Selecting this option would mean that the user will need to confirm their selection and proceed (Figure 1.2).


Figure 1.2 - Confirm Advanced Release Update Option

Once the Release Update Studio is switched to the advanced flow, the Release Update Summary table will display all the options available for a "Build Place With Customizations" (Figure 1.3).


Figure 1.3 - Summary Table after Switching to Advanced Release Update Flow

Few points to note about the Release Update Advanced Option:

The statuses in the summary table that were visible in the "Build Place Without Customizations" will be reflected in the same manner after switching.
In addition to the operations that were available prior to switching, the following will also be enabled; Impact Analysis, Customization Upliftment Preparation, Apply Release Update in Solution Repo, Order Baseline Environment, Order Topic Environment, and Sanity Build.
The Customization Upliftment Preparation operation will work as follows;
If you switch to the advanced view after the 'Apply Release Update to Solution and Sanity Build' step is completed - The 'Customization Upliftment Preparation' step will be marked as N/A and you will not be able to perform an upliftment. This is due to the Build Place not having customizations at the time of switching and hence no upliftment is needed.
If you switch to the advanced view after the 'Apply Release Update to Solution and Sanity Build' step has failed and the new RU version is not updated in the solution repo - The 'Customization Upliftment Preparation' step will be marked as N/A and you will not be able to perform the upliftment.
If you switch to the advanced view after the 'Apply Release Update to Solution and Sanity Build' step has failed but the new RU version is updated in the solution repo - The 'Customization Upliftment Preparation' step will be marked as N/A and you will be able to perform the upliftment.
If you switch to the advanced view prior to starting the 'Apply Release Update to Solution and Sanity Build' step - The 'Customization Upliftment Preparation' step will not be marked as N/A and you will be able to perform the upliftment.
The Order Delivery step can be performed multiple times, unlike in a "Build Place Without Customizations".

Once you switch to the Advanced Release Update process, you can follow the Taking a Release Update to a Build Place With Customizations section of the documentation.

Process of Applying Release Update to Solution and Sanity Build¶

Once the Release Update is applied to the baseline repository, the 'Apply to Solution and Sanity Build' button will be visible. Once the button is clicked you will be asked to confirm the operation to continue (Figure 1.4).


Figure 1.4 - Apply to Solution and Sanity Build Confirmation

The progress will be marked in the Release Update Summary table as shown in Figure 1.5.


Figure 1.5 - Release Update Summary Table when Apply to Solution is In Progress

At this point, the users will not be able to switch to the 'Advanced Release Update' option as the operation of applying the Release Update to the Customer Solution Repository is still in progress (See Figure 1.6).


Figure 1.6 - Advanced Release Update Button Disabled when Apply to Solution is In Progress

Once the operation of applying the Release Update to the Customer Solution Repository and the sanity build process is completed, the Release Update summary table will reflect the change. The "Order Delivery" button is also enabled at this point to continue the Release Update process (Refer Figure 1.7).


Figure 1.7 - Release Update Summary Table when Apply to Solution is Completed