On Jul 4, 2013, at 10:33 AM, Andrew Phillips wrote: >> 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..?
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. Multiple builds close to each would still overwrite each other, the same as with Jenkins workspaces getting overwritten. But I don't see that as being a huge issue. This will be worth investigating. I'll chat with abayer about switching the doc build to CloudBees at the meetup and see if it's easy enough to do. Thanks for the suggestion! Everett
