@abayer Would that Build Secret Plugin be available in our CloudBees instance
when the build starts running? How would that work?
I see what you mean about the jclouds Plugin from the "Publishing artifacts
after a build" section but there might be a blocker. First off it needs to be
able to upload the entire _site dir to a uniquely named container like
_site_${BUILD_NUMBER}. The description on the plugin page makes it sound like
it only uploads individual files.
The other blocker for the jclouds Plugin is a problem I ran into last night.
You need to specify the Content-Type of objects in Cloud Files, otherwise
browsers can misinterpret them. For example, the CSS won't get used properly
because the Content-Type coming back from Cloud Files is application/unknown.
There's a fix for this by setting the Content-Type for the objects individually
as you upload them. I haven't had a chance to fully implement this fix yet
though.
The jclouds Plugin could have other uses for us in the future so go ahead and
pursue it if you like. I don't think we'll be able to use it for the site build
though.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/2#issuecomment-21077204