<baduck>
i've found a bunch of configs. like the openzfs stuff and llvm's zorg (ugh!) and yocto's autobuilder2.
<baduck>
i wonder how people test that stuff?
<baduck>
or debug it.
<glogan>
That was the hardest thing for me at first. The docs kinda dump you in head first without baby's first buildbot config
<glogan>
Very carefully haha
<baduck>
yes. also i have to deal with multiple repositories. the gnupg stuff, if you want to know
<glogan>
That's next for me. We've got the codebase, plus 3 packaging types
<glogan>
Right now the packaging just builds whatever the branch matches, no events at all
<glogan>
Gpg in my docker containers was... Fun
<baduck>
you mean using gpg?
<glogan>
Yeah
<baduck>
i guess you can just schedule full builds if you have the resources to burn.
<baduck>
huh. the self tests just ran successfully. i didn't have to look at that yet.
<glogan>
Always a good sign :)
<baduck>
and code to look for examples :-)
<baduck>
gnupg source has "speedo.mk" that handles building the suite from from-scratch checkouts from all the libraries.
<baduck>
but that doesn't handle incremental builds
<baduck>
anyway, testing has been time consuming and tedious so far. buildbot has a steep learning curve. kinda like climbing the glass front of a sky scraper
<glogan>
If you take the configs in my repo apart it'll at least give you an idea of how configs work
<glogan>
Fortunately they're the same between doing everything in docker vs doing things on for-real hardware