My bad. My frustration and impatience got the better of me. Lesson learned.
It turns out I do have access to the jclouds.github.com<http://jclouds.github.com> BuildHive. I signed in with my GitHub account so maybe it's a function of my GitHub permissions. Everyone should go to the jclouds.github.com<http://jclouds.github.com> config page [1] and see if they can access it. If not, we should fix the permissions so all committers can. I fixed the BuildHive error due to the backwards incompatible change and fixed a deprecation warning too. The build is passing successfully now. I'm still unable to use deploy-site.sh and it appears to be an Apache permissions problem. I'll file an issue with INFRA and see if they can help. Thanks, Everett [1] https://buildhive.cloudbees.com/job/jclouds/job/jclouds.github.com/configure On Jun 25, 2013, at 3:26 PM, Matt Stephenson wrote: Jekyll made some backwards incompatible changes it looks. Regardless, in the future please notify people when you notice the build is failing and it doesn't appear to be your change in particular. I generally ignore when it fails if it's not my pull request, if it's my pull request I always make sure it's clean. Even if it blocks merging it in before fixing something in cloudbees. On Tue, Jun 25, 2013 at 1:00 PM, Everett Toews <[email protected]<mailto:[email protected]>>wrote: On Jun 25, 2013, at 2:36 PM, Andrew Phillips wrote: Could someone with access to the BuildHive job configuration take a look? All committers should have access to all BuildHive jobs. When we run into problems like these we should not have to block on someone with access. We all need the ability to fix these changes. We are all responsible for documentation and it's build process. Can the owner of the jclouds.github.com<http://jclouds.github.com> BuildHive please give all of us access to these jobs? Everett
