Skip to content

Sanity Builds

Overview

This section describe the sanity build process in Release Studio.

Sanity Build Process

Release Studio sanity build process is similar to the Build Place sanity build process except the following differences,

  • Code in release-update branch will be built and deployed instead of master branch code.
  • If the sanity build is successful, Customer solution repository is tagged as san-ru-<Unix Timestamp>-OK. If fails, tagged with san-ru-<Unix Timestamp>-FAILED and a Sanity Image is not created.
  • Only manual sanity is allowed and scheduled sanity is not allowed for the moment.

When the customization uplifment has been completed by following the all the steps in Apply Release Update to Customer Solution Repository and Customization Uplifting Process user can run a manual sanity build through Release Update Studio by clicking on the "Sanity Build" button.

Figure 1.1 - Navigator of the Release Update Sanity Build
Figure 2.1 - Order a Sanity Build Dialog

Note: To generate a successful Release Update Sanity tag, customizations should have been commited to the Release Update branch. When there are no new commits in the customer solution repository Release Update branch, Release Update Sanity tag(eg: san-ru-<unix-timestamp>-OK) will not be created.

Refer Sanity Builds for more information.

Things to avoid

It is highly recommended not to revert the release update related commits. In the event this happens, sanity build might be failed.

In such scenarios, the user is advised to abort the release update process and start as a fresh release update. Please contact IFS support team on release update abort process.