This would have the added benefit that the CloudBees doc build would be (sorta) persistent vs the workspace of the Jenkins build disappearing when the build slave is terminated.
Just to clarify that the docs would actually not be served from the *workspace*, but by some appserver. So in a "vanilla" setup builds would indeed still overwrite each other, but there are perhaps ways to make it more funky and have different PRs published to different context roots, or something like that..?
ap
