Re: Using secret-tool and Gnome keyring to protect Salsa API keys
> Thanks! I gave some comment on the merge request.
Thanks!
> Where are we with enabling Salsa CI pipeline for all Go projects by
> default? Given that Go packages often need new dependencies, I would
> suggest to add `SALSA_CI_DISABLE_APTLY: 0` so that you can easily access
> the Salsa-built *.deb packages for use when building other new packages
> that need a new version of some build dependency.
This is a separate topic from what the subject of this email was, but
it is the same repository. If you want this config, feel free to open
MR https://salsa.debian.org/go-team/infra/pkg-go-tools/-/blob/master/config/gitlabciyml.go
and tag me as reviewer.
The Salsa CI runners are already enabled team-wide, and any new
project created with latest dh-make-golang should inherit
https://salsa.debian.org/go-team/packages/dh-make-golang/-/blob/cdc1ff44fe856edad7767827166e03c91b716636/template.go#L462-510
and any old package needs to run the pkg-go-tools to get updated. This
should be done one-by-one on a package when it is getting other
updates and the person doing it is ready to fix the package if it
didn't pass CI.
Reply to: