Hi Chris, On Thu, 12 Jun 2025 at 17:06, Christopher Baines <m...@cbaines.net> wrote:
> I've started trying to use Codeberg's issue and project tracking > functionality for the qa-frontpage [3][4], and the related bordeaux > build farm [5]. Cool! Thank you for all this effort over the years. > I would like to see some setup for testing Pull Requests raised on > Codeberg, although it's not clear to me how to approach this and I want > to focus on finishing off the work on the existing setup [6]. Some work > towards this has already happened [7], but I'm not aware this is up an > running anywhere yet. Sorry if I’m out of the scope. Well, I’m not sure to get the picture between QA, Data Service, and the two build farms bordeaux.guix and ci.guix. If I understand correctly, ci.guix (Cuirass) already implements something to trigger a build by a Pull Request. And I remember the days where Data Service was collecting data from Cuirass. My question is: in addition to bridging Forgejo with Build Coordinator so then QA and Data Service, could you point where to look to restore a bridge between Cuirass and Data Service and/or QA? Worded differently, do you a rough estimation about how much work it would be? Couple of hours? Days? Weeks? Too hard because of some orthogonal design between Cuirass and Data Service? Well, in order to know if it’s doable by the current Cuirass masters. ;-) Cheers, simon
