Hey! Not much has changed since the last update. There's a new "waiting for builds" status, I tweaked some code around build cancelation, I put in place a mitigation for #67194 affecting the build coordinator, and did some investigation of the hurd locale issue (#67507).
As previously set out, I'm planning to stop hosting the data service instances this year. While I would like to stop hosting the server for data.guix.gnu.org, I am going to keep that going at least for the time being as that will allow me to test out pruning the bordeaux nars among other things. I am still planning to shutdown data.qa.guix.gnu.org and QA which depends on it within the next couple of weeks. I do hope it can return some point though, and hopefully sooner rather than later. On this like most decisions I'm indecisive, I could try and keep the current server going, but it's not the most cost effective setup and it's very low on disk space. I could replace the server with some slightly better setup, but this would still mean I'm managing a key part of the infrastructure, which is something I'm trying to move away from. There was some discussion of the project taking over the hosting, and maybe that will happen at some point, but it hasn't happened yet. So while not having qa.guix.gnu.org for a time isn't ideal, I'm still going with this approach. Given that the first prototype setup came (and went I think) sometime back in 2019 [1], this stuff has been going on for a while now. From that prototyping over the last few years, I think the current software setup is something that can work long term and be iterated on. To take this technical setup forward though, it would ideally happen more through the project and no longer have key parts be reliant on me for hosting. 1: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00089.html Thanks, Chris
signature.asc
Description: PGP signature
