That failure on 250 is due to a slave barf on cloudbees - it can probably be ignored, given that there are enough other builds running. =)
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/156#issuecomment-25269611
