Another option might be to copy the site to S3 or Cloud Files for preview. But that involves saving the credentials in the BuildHive job.

We could also bundle the HTML files up as a WAR and publish them to our RUN@cloud account, as we do with the Javadocs [1, 2].

All it should take is a CloudBees (rather than BuildHive) pull request builder job and some magic to build the WAR file..?

ap

[1] http://javadocs.jclouds.cloudbees.net/
[2] http://javadocs-labs.jclouds.cloudbees.net/

Reply via email to