You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@hnestmann@tobiaslohr
feel free to mark it as duplicate but this is what -to my view- we've concluded (After #20 discussion):
2 types of support
file detail level
using a kind of deploymentinfo.json file as parameter (created from SCM info as a preprocess before calling sfcc-ci) that keeps track of every single file (vs last deployed code version) added/removeed/changed
cartridge level
pushing the whole list (as parameter) of cartridges you wanna completely overwrite (no diff, just replace every cartridge in the list of the last deployed code version)
(there could be a folder level too)
working as cartridge level one but only for listed cartridge (even using wildcards) +folder/subfolder (i.e. static folders)
Thanks
The text was updated successfully, but these errors were encountered:
@hnestmann @tobiaslohr
feel free to mark it as duplicate but this is what -to my view- we've concluded (After #20 discussion):
2 types of support
using a kind of deploymentinfo.json file as parameter (created from SCM info as a preprocess before calling sfcc-ci) that keeps track of every single file (vs last deployed code version) added/removeed/changed
pushing the whole list (as parameter) of cartridges you wanna completely overwrite (no diff, just replace every cartridge in the list of the last deployed code version)
working as cartridge level one but only for listed cartridge (even using wildcards) +folder/subfolder (i.e. static folders)
Thanks
The text was updated successfully, but these errors were encountered: