Skip to content

Sanity Builds

Sanity Build Process

The Sanity Build Process is used to assess that the latest revision in the master branch of the Customer Solution repository is buildable.

During this process, the code in the master branch is built and deployed. Several criteria are checked which include Database code generation, Database code deployment and code compilation.

If no errors are found, a Sanity image is created and the master branch of the customer solution repository is tagged as san-<Unix Timestamp>-OK. However, if the build fails, the master branch is tagged with san-<Unix Timestamp>-FAILED and a Sanity Image is not created.

The sanity build tags for the customer solution can be viewed on the Azure repository as shown below.

When ordering a DEV or a QAS Environment from the IFS Lifecycle Experience Portal for development or testing, the latest successful build with sanity passed is used to create the environment.

[!IMPORTANT]

It is recommended to run a Sanity Build following a series of customizations in the Customer Solution Repository. Regularly performing Sanity Builds helps to verify the integrity of the build process and ensures that the customizations have been successfully added. This practice enhances the reliability and stability of the final build.

The sanity build should be manually triggered through the Sanity Build button in the Build Place.

When the Sanity Build button is clicked, the panel below appears. Select the relevant commit from the Target Commit dropdown and click Order to trigger the Sanity Build up to the selected target commit.