Hi all,
Personal opinion about the "old" CI
I don't have any strong opinion nor the energy to argue about keeping the current Go Team specific CI versus abandoning it in favor of the "standard one". I see advantages in both system.
The idea of the "old" CI was to trigger a massive rebuild of all go packages each time a new version of given package is pushed. This works very well in theory and allowed us to catch breaking changes without having to rely on ratt. Building the whole "world" used to took less than 30sec on a good machine with an up-to-date cache. This is why this CI was so appreciated and useful. The problem is that it is no longer maintained and therefore may break and cause negative impact on the developer experience. Maybe it only need a brush up? Maybe keep both system could be useful ?
About pkg-go-tools
pkg-go-tools is the home of the pgt-api-server (who runs at https://pgt-api-server.debian.net/ and is managed by myself).
The pgt-api-server is invoked by both dh-make-golang(1) and gophian(1) to setup the Go repository following the team best practices [1]. I don't think dropping this would be very helpful as it would break existing version of tools who are in the Debian archive, and it will requires us to find an alternative way to setup Go repository. The current approach is configurable (we only need to update config.go to apply team wide policy change on Go repositories, no need to update the tooling) and I think it is worth keeping it.
This repository also host several useful tools such as ci-config (used to apply the current team config to all repositories), ci-build (the Go team CI), etc...
If we want to move on depreciating those tools anyway, I don't think it would be a good idea to delete the go-team/infra/* repositories, archiving them would be less dangerous.
About provisioning
The 2 repositories are just Ansible files used to boostrap easily a CI runner as well as a pgt-api-server. They should be kept if we are keeping the previous repositories, otherwise they should be archived.
---
While I am still subscribed in the list, I found very hard to find time to answer. Thank you Nilesh for quoting me because it pushed me to do so. And sorry in advance if my mail may sounds hostile or rushed, it was written between two meetings while I took a much needed coffee break.
Cheers,
[1]: https://salsa.debian.org/go-team/infra/pkg-go-tools/-/blob/master/config/config.go?ref_type=heads
[ CCing Alois and Shengjing ] On 12/05/25 11:43 pm, Otto Kekäläinen wrote:I didn't get any responses to this email last month. I guess people active on this list don't have knowledge/opinion about these?I don't have detailed knowledge about any of this, but have you taken a look at [1] yet? Maybe [2] also helps? [1] https://go-team.pages.debian.net/ci.html [2] https://lists.debian.org/debian-go/2021/08/msg00005.html Thanks Nilesh