On Sep 14, 2014, at 5:09 PM, exarkun@twistedmatrix.com wrote:

Hello,

I noticed that https://twistedmatrix.com/trac/ticket/7355 is a blocker for the release of Twisted 14.1 and #7355 is blocked Python 3.3 buildbot configuration/availability issues.

Thank you for (specifically) bringing this up and (generally) getting the 14.1 blockers cleared out. I'm beginning to notice a concerted effort :-).

Who can look at why one of the Python 3.3 slaves is offline and why the two slaves are configured differently?

I've been gradually accumulating the various credentials that I need for maintaining all the buildbots. On my to-do list is centralizing and documenting how all of these are maintained to make it a bit less obscure. It may surprise you that you personally actually have access to those credentials! For the time being I've sent you a separate personal message explaining how you might get access to it, although I apologize that that's as good as we can do right now. This isn't exactly blocked by the following ticket, but filing this is the last thing I did while trying to figure out the Python 3 buildbot situation: https://fedorahosted.org/fedora-infrastructure/ticket/4518 I will probably have another look at this tomorrow whether it's fixed or not, but I certainly wouldn't mind if some other folks bumped that ticket and politely reminded the Fedora infrastructure team that invalid certs are a pretty serious operational issue. -glyph

On 15 Sep 2014, at 14:16, Glyph wrote:

On Sep 14, 2014, at 5:09 PM, exarkun@twistedmatrix.com wrote:

...

Hello,

I noticed that https://twistedmatrix.com/trac/ticket/7355 is a blocker for the release of Twisted 14.1 and #7355 is blocked Python 3.3 buildbot configuration/availability issues.

Thank you for (specifically) bringing this up and (generally) getting the 14.1 blockers cleared out. I'm beginning to notice a concerted effort :-).

Thanks, exarkun, Glyph, as well as the others which have helped fix tickets and help things along for the 14.1 release — it’s not going to be long before I can get 14.1pre1 gracing all your hard drives! <3 -hawkowl

On 15 September 2014 07:38, Glyph wrote: [snip]

Special privileges are required because one of the aspects of buildslave maintenance is cloud control panel access to the cloud providers that maintain this hardware, which, if abused, could end up billing the non-profit which manages Twisted's funds an unlimited amount of money. The buildbots are also managed via shell accounts, which could of course be used to deploy malware.

If you are interested in helping to perform maintenance on the buildslaves, access to those permissions could be arranged for you. It had not occurred to me to ask you before, because if I recall correctly, you'd refused commit privileges when they were offered in the past.

-glyph Sorry for the delay.

I would like to help the Twisted project in any way... including with buildslave maintenance. I think that at this level I only need ssh access. -------- I refused commit privileges as I wanted to contribute more patches and do more reviews as a read-only contributors, before starting to mess with Twisted repo. I think that it would be nice to have some process to initiate new contributors to the whole review process and once one or more senior-reviewers consider that the new contributors is good to do reviews by itself, to give him commit privileges. Cheers, -- Adi Roiban

On Sep 14, 2014, at 5:09 PM, exarkun@twistedmatrix.com wrote:

Hello,

I noticed that https://twistedmatrix.com/trac/ticket/7355 is a blocker for the release of Twisted 14.1 and #7355 is blocked Python 3.3 buildbot configuration/availability issues.

Who can look at why one of the Python 3.3 slaves is offline and why the two slaves are configured differently?

The configuration of the two slaves has been made consistent, and I have reviewed and landed the relevant ticket. At long last, that particular square on the build matrix is green. -glyph