IFS Cloud - Method of creation ordered environment

I found this:
Lifecycle Experience Portal Troubleshooting Issues - Technical Documentation For IFS Cloud

But still does not understand, how it works.

How is TOPIC environment created?

DB deployment logs contains all modules and modules are installed in “Up To Date” mode, so there must be some snapshot of db on top of is delivery with topic branch content installed. (also it looks like there is no diffs and delivery is builded on whole build checked out from topic branch).

What source have this snapshot? 

Does sanity build do full fresh install to some snapshot, what is used for ordering DEV env? And as base for TOP environment?

Currently it look like it work this way:

• DEV
  • Created from last successful Sanity Build
  • Import All Test Data
• TOP
  • Build delivery from all commits in master branch from last successful Sanity Build
  • Created from last successful Sanity Build
  • Applied delivery
  • Import All Test Data

But I still does not know, if Sanity Build application is some snapshot or installed as Fresh install or as Patch.

HI @InfFilipV 
I can give you a 10 min feedback whats my opionion on this via teams since you asked in the other case. 
I do not have time to answer you here this week. I am sorry!

Hi @InfFilipV ,

Based on the questions/concerns raised regarding the cloud product, the recommendation from IFS Support is as follows,

Please complete the basic training in the academy for IFS Cloud Build Place.

1. IFS Cloud Essentials: https://ifs.sabacloud.com/Saba/Web_spf/EU2PRD0185/app/me/learningeventdetail;spf-url=common%2Fledetail%2Fcours000000000009840%3FfromAutoSuggest%3Dtrue

2. Awareness Week - IFS Build Place: https://ifs.sabacloud.com/Saba/Web_spf/EU2PRD0185/app/me/learningeventdetail/cours000000000010962?regId=regdw000000000306351&returnurl=common%2Fsearchresults%2Fcloud%20build-place%2FALL

3. Best Practices and Guidelines for CRIM Development (Academy): https://ifs.sabacloud.com/Saba/Web_spf/EU2PRD0185/app/me/learningeventdetail/cours000000000010520?regId=regdw000000000301907&returnurl=common%2Fsearchresults%2Fcrim%20build-place%2FALL

Other useful resources from product documentation :-
1. IFS Lifecycle Experience Guide (docs.ifs.com): https://docs.ifs.com/techdocs/21r1/Foundation1/047_lifecycle/default.htm
2. Tailoring Guide (docs.ifs.com): https://docs.ifs.com/techdocs/21r1/Foundation1/060_tailoring/default.htm

Best Regards,

Shirantha

Hi,
I had call with @Rusiru Dharmadasa , so to make this question up to date:

Learnings:
1) IFS Cloud Essentials
- there is no technical details
2) Awareness Week - IFS Build Place
- "This course has been discontinued"
"Discontinued on:11-SEP-2021"
3) Best Practices and Guidelines for CRIM Development
- Already Done, and this is not covered here

Process:

1. BaseBuild is build and installed to ENV
   • Snapshot of DB is stored
2. Sanity Build
   • Delivery is build from commits above previous sanity-tag
   • Delivery is applied on top of environment created from stored snapshot  of previous sanity build
   • Snapshot of DB is updated
3. On Environment Order is:
   1. for TOP/DEL - Created delivery
      1. TOP - from all above last sanity-tag
      2. DEL - from chosen bunch of commits from master
   2. Created “machine”
   3. Restored snapshot
      • TOP from latest SanityBuild
      • DEL from latest Delivery (???)
   4. for TOP/DEL installed delivery
   5. for DEL - store snapshot (while is delivery approved are stored two snapshots, on approve is old one deleted)
   6. execution TAR scripts

Answers are:

• All deliveries are build in “up to date” mode - CRE files are not executed
• there is snapshot used
  • this mean problem with “Revert commit” on master branch after sanity build, because for next environment creation will be used snapshot with reverted commits included
    • Reverts should not be done ( - should be disabled in DevOps)
    • Reverts must be done with IFS assistance to restore previous snapshot (if possible)
    • Or Reverts are impossible and Drop scripts must be created
• Non-Standard DDL construction could be done in Dynamic SQL Block (credits to @JohannesKnust )
  •  

    

    ​​​​​​

@Rusiru Dharmadasa : could you please correct me, if I’m wrong?

BR

On 29.4.2025 I’ve received this description of environment creation process:

The way Topic & Sanity Build databases are created is fundamentally different to the way the delivery environment is created:

The Topic & Sanity Build databases in the Release Update Studio are recreated from scratch by taking a copy of the the corresponding Core image for the version you are going to and subsequently deploying all the code in GIT to it.
The Delivery database is created by taking the latest delivery database image from the customer's Build Place (so from the previous version) and deploying the RU on it.

For Topic & Sanity Build databases the CMOD component does not exist at all yet in the database (as it is not part of the Core image) and the fresh install will create the tables from scratch using the CRE files.
For Delivery databases the CMOD component already exists and, if the deploy.ini is configured properly should be treated as "Upgrade" (executing UPG and CDB files) or "VersionUpToDate (executing just CDB files).

We have also raised a ticket for RnD with the plan to do an enhancement in the future to raise a build error if the version of the component in the database is not present in the deploy.ini instead of falling back to "FreshInstall" as it does at the moment. This should give a more meaningful error to action on (helping technicians to help themselves!).

What is in conflict with previous informations given, but maybe it is related only to RU process.

25R1 Release Notes informs, that *.storage files won’t more support “Non-Standard DDL constructions“ via BEGIN END Blocks

ifs.sharepoint.com/sites/IFSCloudProdInfo/Release Documents and Links/Forms/AllItems.aspx?id=%2Fsites%2FIFSCloudProdInfo%2FRelease Documents and Links%2FRelease_Notes_Summary_IFS_Cloud_25R1_EA.pdf&parent=%2Fsites%2FIFSCloudProdInfo%2FRelease Documents and Links