Shengjing Zhu <zhsj@debian.org> writes: > On Tue, Sep 9, 2025 at 11:16 PM Otto Kekäläinen <otto@debian.org> wrote: >> >> Hi! >> >> On this list we have had several discussions about CI. Historically >> there has been a debian/gitlab-ci.yml that ran a custom Go >> `test_the_archive` job on a custom Go runner. As discussed on this >> list several times in past year, it does not seem to provide much >> value right now, as it does not fail even if the package itself is >> unbuildable. >> > > Could you do better research before proposing changes? The two CI have > different goals which I have explained in several emails. How about this: 1) We change Go policy to use debian/salsa-ci.yml like the rest (?) of Debian. 2) Our template debian/salsa-ci.yml contains: include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml - https://salsa.debian.org/go-team/infra/pkg-go-tools/-/raw/master/pipeline/test-archive.yml 3) We enable shared runners on all projects (I think this may have already been done). This would make both the old "test_the_archive" job run, and the standard Salsa CI pipeline. And avoid having to discuss the merits of each pipeline system, which I think we just never seem to reach any consensus on, and discussion just deteriorate. Maybe it is fine to simply disagree on that, and let both set of pipelines run? I think they work fine together. /Simon
Attachment:
signature.asc
Description: PGP signature