Switch to buildbot 2.x

[raimue (Rainer Müller)]

We need to look into updating to buildbot 2.x, which requires updating our buildbot master.cfg and testing the builds.

This depends on having buildbot 2.x in the ports tree, see #53006.

[ryandesign (Ryan Carsten Schmidt)]

I want to try this out. I know that Rajdeep worked on this; I see he has a repository with a buildbot 2 configuration last modified 14 months ago. Is that the most recent work on this? Is there anything else I need to know before checking out that repo and trying to follow the instructions?

[ryandesign (Ryan Carsten Schmidt)]

Mojca, Rajdeep, and I have been talking about this over email. I have a buildbot 2 server running now, doing mainly fake builds, while I work out how I want it all configured. Much of the buildbot 0.8 configuration has not been migrated yet.

[mascguy (Christopher Nielsen)]

Any progress on this?

While the upgrade as a whole would certainly be awesome, I'm particularly interested in OAUTH integration - and ultimately being able to use GitHub authentication - per issue:52455

[ryandesign (Ryan Carsten Schmidt)]

Nothing to report. I did not complete a buildbot 2 configuration last year and have not been motivated to revisit it since then because buildbot 0.8 works for us while later versions have been redesigned and both the new back-end and the new web UI experienced extreme hangs (at 100% CPU usage for a very long time) in my testing, not to mention that they removed the waterfall web UI upon which I almost exclusively rely. GitHub authentication is not possible with Buildbot 0.8.

[mascguy (Christopher Nielsen)]

Just curious, was the waterfall view eliminated as of v3.x?

[mojca (Mojca Miklavec)]

Waterfall has been radically changed in version 0.9 already. It wasn't eliminated, but it's significantly different now, and the sample setup that we came up with now uses a separate virtual builder for every port and Ryan wasn't happy about that. (Without a separate virtual port one has no clue what exactly is being built since the labels on waterfall are gone now.)

[ryandesign (Ryan Carsten Schmidt)]

The old waterfall view was eliminated. A new view called waterfall was added that behaves differently and shows less information. When all builders were busy, the waterfall view caused Safari to use 100% CPU and become unresponsive until the builds finished, rendering it useless for being able to see what's going on. In addition, the introduction of the virtual builders brings new complications; it now becomes difficult to see what a particular builder is doing.