Timeline for How to build manual Sitecore Packages for deployments?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2018 at 15:49 | history | edited | Michael West | CC BY-SA 3.0 |
Changed the title.
|
| Mar 2, 2018 at 15:33 | answer | added | jammykam | timeline score: 5 | |
| Mar 2, 2018 at 14:48 | vote | accept | Michael | ||
| Mar 2, 2018 at 14:35 | answer | added | jrap | timeline score: 8 | |
| Mar 2, 2018 at 14:20 | comment | added | Michael | @jrap, thanks, sounds correct indeed. Although I never choose the merge option on installing a package manually. | |
| Mar 2, 2018 at 14:16 | comment | added | jrap |
For manual deployments like that, I would choose the entire User Defined folder, just to make sure you don't miss anything- a merge could alter the last updated date and you could miss it. There are automated methods for doing this, but can't be answered in a concise way for SSE.
|
|
| Mar 2, 2018 at 14:14 | comment | added | Michael | On the other hand, what am I doing!? Is it that wrong not to include the full "user defined" folder? :P | |
| Mar 2, 2018 at 14:11 | comment | added | Michael | @jrap 1. triggered after creating package that way for content changes 2. laziness for selecting them specifically 3. rather having efficient small packages that only contain the changes to be done on dtep environments. | |
| Mar 2, 2018 at 14:08 | comment | added | jrap |
Other than it taking longer to install, there should be no reason you can't select all templates items at your custom templates root folder (possibly User Defined). Since your code is dependent on templates existing, selecting all of them ensures your code/templates are a 1 to 1 match. Why are you pursuing this option?
|
|
| Mar 2, 2018 at 14:04 | history | asked | Michael | CC BY-SA 3.0 |