Build Place

Hi @Arifmd1705 ,

Sanity build will check out the latest changes to the master branch (commits performed by the technicians/solution developers) and asses if the underlying codebase is buildable. In the build-place, the master branch of the solution repository will be built using an automated pipeline job and in the Release-Update studio, the release-update branch will be used during the sanity build process.

If the automated job initiated for the sanity build is successful, log files will be available on the LE portal and a tag will be introduced to the latest commit revision on the master branch (if you are working on the RU studio, the sanity tag will be applied to the release-update branch). The automated job will create internal azure resources (virtual machines and other relevant resources) to generate the code base and deploy it. If the job is successful, the VM image will be captured and saved. This VM image will be used for buildplace DEV, QAS environment process.
 

Sanity scheduling process no longer available from 22R1 onwards.

Best Regards,
Shirantha Herath
https://www.linkedin.com/in/shiranthaherath/

​@Shirantha Herath you and the documentation only mention DEV and QA environments are built from the last successful build with sanity successful. Is this true for topic environments as well? My suspicion is that the answer is yes. We recently removed all configurations from our customer solution appconfig directory, all merged and approved to master with no conflicts, and updated topic branch with the latest master. However, when we are now trying to order a topic environment it fails and the logs refer to old CFP that are not present on master or the topic branch and should not be considered in the build according to the LE docs.  Environments created from a topic branch - LE Documentation For IFS Cloud

It currently reads as if it should pull directly from the current master branch