Thanks for providing that link, it showcases my same complaints in the past
I think it's fair to say that anyone with comments about this should have done the following:
Read the code.
Setup, manage, use buildmaster.
I was 80% onboard with it after getting some community input and trying to remove my own biases.
After around 6 months to a year of hacking on it I had to stop and realize I was dumping man hours into something I really don't agree with design wise (mostly no clients and not running as a service) and writing wrappers to try and make it viable solution.
I have to ask, do you have a few hours a week to do the following work:
- Make it run as an http rest service
- Make the clients poll for work from the server
If buildmaster had those things, we would be using it right now and not kitchen. Those are important features so we can grow it long term. Those features also mean buildmaster core functionality ends up not being a bunch of hacked shell scripts.
At this time, nobody has stepped up to do the work, and I don't have enough faith in buildmaster to do it myself. (And I have trouble finding motivation in writing things in langues I don't like when I'm not getting paid to ).
Package repos have been one of the final few blockers to r1. Our developer base is dwindling. Let's just get this crap done already. (Which is what kitchen does)