Hi! Go team feedback about Salsa CI docs in particular about runners is still welcome as you have expertise running your own :)
Related, I was recently working on a Go package and ran into CI issues with my fork, but I solved it and you can solve it for all Go team packages if you merge this: https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/1 On Tue, 17 Sept 2024 at 01:16, Otto Kekäläinen <[email protected]> wrote: > > Hi! > > I noticed the Go team has docs for having your own Salsa CI runner: > https://go-team.pages.debian.net/ci.html > > There are also Ansible scripts to deploy it at > https://salsa.debian.org/go-team/infra/provisioning/-/tree/master/ci-runner, > though the runner configuration is not fully identical to the docs. > > Perhaps this practice of having team-runners would make sense for > other teams as well? > > We recently added in Salsa CI the doc > https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/RUNNERS.md, > and I wanted to invite you to contribute to it in case you have best > practices to share or if somebody wants to refactor the Ansible script > you have and make it generic enough to be something we could recommend > for any team or DD to use across Debian, and potentially distributed > as a single file/directory from a centralized place. > > - Otto
