On Wed, Dec 4, 2013 at 7:49 PM, Chris McMahon <[email protected]>wrote:
> There seems to be an issue with our account at Cloudbees such that all of > the builds are suspended in a failing state right now. > #TLDR It was my fault. Again. Sorry about that. :( Good news is that I have fixed the problem! :) # The story I was trying to help a Google Code-in student (Hi Geoffrey!) on a Jenkins related task he is working on[1]. We have a Jenkins instance at Cloudbees[2] and since we are out of accounts, he has created his own instance[3] where he can run test jobs. I was setting up jobs there, created Sauce Labs service (think Selenium in the cloud), but I was not sure if Sauce could charge him, so I have decided to cancel the service. Boooooom! Looks like I have canceled our Sauce service. I am not sure how that happened, but it did. Maybe Cloudbees got confused, but more likely I got confused. Anyway, I have fixed the problem, it should never ever (ever!) happen again. To remind myself to never ever (ever!) to cancel services that we use, I will write a script that will output 100 times "I will never ever (ever!) cancel services that we use." Željko -- 1: https://bugzilla.wikimedia.org/show_bug.cgi?id=55824 2: https://wmf.ci.cloudbees.com/ 3: https://geofbot.ci.cloudbees.com/
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
