[ERM-5] A diagnostic tool on rollout problems (+ possibly, activation problems)

[smiakchilo]

In real-world practice, a rollout fails from time to time with reason unknown to the operator. This can be due to:

• missing or corrupt MSM configuration
• missing jcr:content node in a target folder or one of the intermediate ones
• an MSM config loop, and more
  Would like to have

1. a success or failure message upon the rollout of a particular page
2. either a diagnostic UI that analyses and reports possible rollout problems or detailed feedback on why the rollout failed in the very rollout UI, or both

[liubou-masiuk]

MVP discussed with @smiakchilo
Either perform rollout diagnostics before the rollout, or during the rollout (whichever is easier)
If there are any known** issues with rollout, inform the user about

• the page that is rolled out
• rollout source and target
• failure reason

** known reasons for rollout failure:

• jcr:content of the page is absent in the livecopy
• the page is in cq:exclude list
• (optional) on the livecopy level the author disabled the inheritance for page's children. then the children are rolled out from the blueprint. this results in a rollout conflict
• (optional) circular rollout depencenies (which can lead to endless rollout)