Hi all, > 4. Start running Salsa CI on Go team packages manually > > The current Go team CI run is incomprehensible to me. It does at least > *not* test the most important thing a CI in Debian should do, which is > to tell if a package builds in Debian or not. This can be fixed right > away by making manual extra Salsa Ci runs easy with > https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/2 > > 5. Enable Salsa instance runners in Go team and run Salsa CI automatically > > Once 4 is done, we can further tweak the Salsa CI template to best fit > Go team, and in maybe 3 months follow up by getting a setup that > automatically runs at least the package build, autopkgtest and Lintian > jobs from Salsa CI.
This suggestion 4 was merged in https://salsa.debian.org/go-team/infra/pkg-go-tools/-/commits/master. Anyone using this tool should get the new Salsa CI in their project and can start running Salsa CI manually to get more experience of it.
