Hello Simon, Simon Josefsson <si...@josefsson.org> writes:
> I think documenting step-by-step instructions for setting up a build > server and the steps involved to monitor the health of such a machine > would be good -- I think I offered some machines earlier, and I'm not > sure they are still used and who looks after them, and what the > expectations are, and I could help with it if I knew what to do. As you might know, we have not just one, but two separate build farms, each running its own build software. It’s questionable, but that’s the way it is. :-) There are instructions in the Guix manual and in the Cuirass manual on how to set up Cuirass, the one running on ci.guix. For bordeaux.guix and related services (qa.guix, data.qa.guix, data.guix), it’s a bit more involved (and less documented), but that’s also because it has a broader scope. Typically, we should improve documentation for this, and I think Andreas was looking into it. > Btw, the 'sjd-p9' ppc64el build server could to be upgraded from the > debian bullseye that it is running now. If it is used? It seems be > busy building things though. It is used; you can see it at <https://ci.guix.gnu.org/workers>. It provides lots of substitutes for ppc64le, together with the second POWER9 box that we have (actually a VM). > How about adding another ppc64el build machine on a fresh host (I have > another Talos II around and finally got stable network connectivity for > it) -- while developing the documentation/instructions -- and then once > completed and operational, tear down the current sjd-p9 machine and > re-install it using the new instructions? We could do that yes. And yes, documentation on how to set up individual build machines specially for ci.guix (in this case) probably needs to be written. Thanks, Ludo’.
