> Worth closing/reopening this to see if it was a transient failure on their > side?
Looks like the job configuration was borked :-( I've cloned the job but the clone also wasn't happy - have opened a ticket with CloudBees. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/3#issuecomment-20970645
