Comment 9 for bug 1096126

Right, I suspect there will be a few hurdles with this using Jenkins and CloudSItes (which is probably part of why it hadn't been done previously). First, there's overlap with output from some doc jobs going into common locations, so wiping anything unknown to one doc build would inadvertently blow away content from other builds--this could be addressed by thoroughly siloing the docs publication such that it always uploads into non-overlapping destinations (per release and per job). Second, mass-deleting and replacing on publication will leave brief but frequent periods of time where content is unavailable on the site.

Alternatives to the above involve determining what additional upload mechanisms are available in CloudSites and installing (or possibly writing) a new Jenkins publisher plugin/utility, or switching to a different hosting platform which provides greater built-in fexibility for things like this.