Rather than reviving this dead topic I am starting fresh here.
It has been sitting on my todo list since December, and I finally got around to poking at this automatic builder again.
@anttix, I couldn’t fork your repo, because you forked it from Marlin, and I already have a fork for Marlin. I also wanted to do it a little differently, but with a similar goal at the end. The major difference is that I don’t commit Marlin to my repo at all. I just check it out in the workflow, configure it, build it, save the firmware file, and zip the Marlin folder and save the zip. I pick which branches to build against manually in the matrix, which is currently set to 220.127.116.11 and bugfix-2.0.x.
I have been playing with it for about a week for an hour here or there. It seems to be working pretty well. There are a few hiccups, but it’s generally cranking.
There’s no guarantee this will end up being the defacto configuration tool for Ryan’s firmware. It is a lot harder to tinker with one firmware at a time, but it also does keep the multitude of configurations a bit more consistent.
I still need a good way to provide the artifacts, especially ones that have been “released”. I am wondering if it is worthwhile to make a simple js tool to lead users to the right firmware version. There is an endless amount of automation this opens up if we let it.