All source code will be stored in a git repository.
If developing customizations locally outside preferred Life Cycle build place (where all builds and sanity deployments are made automatically by a simple process in the LE portal), the IFS cloud released source code need to be cloned to a local git repo, where customizations can be developed using IFS Developer tools.
The first build is made on the entire code base in git. Read more here Create a build structure & Build a build_home
After that only deltas of changed files are checked out from git an placed in a separate delivery folder. This folder is first converted to a partial build structure (including any changed library artifacts) and is then referenced to from the build_home to compile the new code. Read more here Create a build structure & Build a delivery
When a new Service update or release is to be applied the new service update code base from IFS release git repository need to be merged into the local git repo. This is done using the Update Analyzer. When the merge is complete a normal delivery delta check out can be made/compiled and delivered.