On Fri, Sep 14, 2018, at 14:02, Zachary Ware wrote:

Hi all,

Most of my effort this week has gone into improving the state of buildbot.python.org, which has largely gone into improving Buildbot itself. Here are the relevant highlights:

• Anyone can now log into buildbot.python.org via GitHub by clicking the 'Anonymous' dropdown in the upper right corner, then 'Login with GitHub'. The first time, GitHub will ask you for approval; subsequently you'll just be logged right in.

• Stopping builds and triggering rebuilds is now restricted to members of the python-core team and the "owner" of a build. I've not had opportunity to test whether the author of a commit actually qualifies as the "owner" or if only the committer does, but if anyone runs into trouble with it please open an issue on the buildmaster-config repo.

• Disabling/enabling schedulers is now restricted to members of the python-release-managers team. We had an issue some months ago where someone had apparently disabled the scheduler for one of our branches, resulting in no builds on that branch for several days before we noticed. That shouldn't happen again!

• Buildbot now reports results from our stable builders on each tested commit. For now, we're still only running tests post-merge, so you won't see new status checks on PRs, but you can find results on https://github.com/python/cpython/commits/

Let me know if any of these changes negatively impact you, or if you have suggestions for further improvement.

Thanks for all your work.

On Sat, 15 Sep 2018 at 07:02, Zachary Ware zachary.ware+pydev@gmail.com wrote:

Hi all,

Most of my effort this week has gone into improving the state of buildbot.python.org, which has largely gone into improving Buildbot itself.

[snip]

Very nice!

Cheers, Nick.

-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia