Doesn't buildbot have dynamic workers implemented as latent workers? [1]
What do you mean by underpowered buildbot steps? Are you implementing your own step classes?
[1] https://docs.buildbot.net/current/manual/configuration/worke...
What do you mean by underpowered buildbot steps? Are you implementing your own step classes?
[1] https://docs.buildbot.net/current/manual/configuration/worke...
In terms of underpowered build steps, I have several fairly complicated, 1k-2k line build factories, with multiple codebases and hundreds of steps (some custom, some from the stdlib). There's many dependencies between the steps, and many different properties that can be toggled in the UI. All these steps need to be defined up-front in the master, but their actual execution often depends on runtime information, so it becomes a mess of doStepIfs. I think it would be an improvement to give a program on the worker the power to tell the service what it wants to do, rather than the other way around.
Agree with you on the waterfall UI regression. It seems console view is preferred than waterfall in the recent versions. It's slower than waterfall UI though.