@abayer @demobox @mattstep In addition to the credentials, another issue with using a simple web server somewhere is keeping multiple builds of the site around. To avoid the changes, we would have to deploy to root thus overwriting whatever else was there. That would make it difficult for committers to review a rendered change made by a non-committer. This is an important requirement.
That simple web server would also need to be maintained. Versus zero maintenance for CloudBees. I agree that having to make changes to support a test env isn't ideal but sometimes it's necessary. Take the VisibleForTesting annotation in Guava for instance. The whole reason that exists is sometimes you need to make trade offs to enable testing. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/2#issuecomment-20851873
