Timeline for Sandboxes often reshuffles files like page layouts making it less git-friendly
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2023 at 12:09 | comment | added | Freddy |
TLDR: Admins have limited interaction and do not have local version of the project. They therefor do not have access to a proper pull as they can only pull via CICD which is similar to retrieving all components in the repo as the CICD always starts with zero source tracking information. This de-facto full pull results in shuffled around files being pulled.
|
|
| Mar 3, 2023 at 9:34 | comment | added | Freddy | Hi @sfdxcfox, thanks for your comprehensive answer. To give important insight into our cicd setup, we have two roles Devs and Admins/No-Coders. All issues related to the question are for the Admin-Setup. Our Admins have 3 ways to interact with their and the target sandbox: pull changes from their sb, push to their sb (in dev terms to "sync" their SB/merge develop into their sb) and deploy the pulled changes to the common integration sb. Pulling via CICD from their SB is de-facto the same as retrieve -p force-app but relying on the SourceMember instead of the files already under force-app. | |
| Feb 24, 2023 at 15:34 | history | answered | sfdcfox♦ | CC BY-SA 4.0 |