Implemented iterative deploy framework and iOS specific implementation
When utilizing iterative deploy in conjunction with incremental cooking only the changed items are pushed to the device resulting in potentially far faster iteration times.
#ios
#codereview daniel.lamb, marcus.wassmer, chris.babcock, josh.adams
[CL 2386082 by Peter Sauerbrei in Main branch]
- Added changes to IPP to allow SSH commands to run as opposed to RPC. This is configurable through the commandline.
- Remote Tool Chain fixes for SSH which were preventing downloads to work. Updated rsync command command
- Removed the ParseProjectSettings calls from some IOS tool chain functions as they were unnecessarily going back through the config cache.
- Added an SSH Command Helper to IPP
- UBT passes SSH details through to IPP on commandline.
[CL 2385579 by Terence Burns in Main branch]
* Moved Slate.h into SlateBasics.h and began shifting less commonly used headers into SlateExtras.h.
* Slate.h now simply includes SlateBasics.h and SlateExtras.h.
* Slate.h includes a deprecated warning now to indicate that SlateBasics.h + specific includes should be used instead.
* Moved dozens of inlined functions using Slate widgets into .cpp files to avoid header dependencies.
* All code samples now include SlateBasics.h and SlateExtras.h so future shifts will not break most those projects, but not trigger the deprecation warning of including Slate.h.
#BUN
[CL 2329610 by Wes Hunt in Main branch]
- Add checking of validity dates on mobile provisions and signing certificates, choosing only ones that are currently valid
- Add extended logging for found mobile provisions and signing certificates, to help debug possible provisioning issues in the future
- Remove duplicated Apple chain certificates from DotNET/IOS and switch to using the ones in Engine/Build/IOS
- Various other output logging improvements and time stamps during code signing
- Remove rotted -interactive option and associated code
- Fix unused variable warning on mono
For release notes: iOS deployment from PC requires the machine date/time to be reasonably accurate (date/time checks are now in place to filter out expired mobile provisions and signing certificates, preventing various deployment issues, but they rely on the machine time being correct)
#codereview peter.sauerbrei, josh.adams
[CL 2268101 by Michael Noland in Main branch]
