Publish pipeline changes
The publish process benefitted from a couple of minor improvements.
Publishing to Content Delivery
The publish (FeedSDLLiveContent.ps1) and synchronize (SynchronizeToLiveContent.ps1) code responsible to upload and prepare material in the Content Delivery stack have been enriched with retries. In their matching .config files you can configure the number of retry attempts (livecontentrequestretries defaults to 1 retry and livecontentprepareretries defaults to no retries) and time between retries (livecontentrequestwaitbetweenretries and livecontentpreparewaitbetweenretries default to a 30 seconds timespan) for regular and prepare calls. The end result is that a single failing file upload because of network glitches will not fail the complete EXPORTFORPUBLICATION event handled by the BackgroundTask service. [TS-10242]
Debugging publishing to Content Delivery
To allow easier debugging, we already generated a __publish.cmd that allows you to reexecute the POSTPROCESSING step.
We now generate an extra file __FeedSdlLiveContent.ps1 per publication export that handles the Content Delivery part of the POSTPROCESSING. So in essence it is a subset of __publish.cmd that almost immediately starts addressing the Content Delivery upload.
Other
Unexisting folder path to a style processor can make cscript.exe hang. A pro active check on file existence should avoid this. [SRQ-1540]