Skip to content

Use standard Salsa CI with standard settings instead of custom Go team CI #279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ottok
Copy link
Contributor

@ottok ottok commented May 15, 2025

Instead of having both the Go team custom CI and Salsa CI, simply use the default template with minimal customizations from https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/recipes/salsa-ci.yml

This simplifies the CI and continues to give the same benefits as before, as the Salsa CI pipeline jobs have made the custom Go team CI obsolete.

The same CI template at https://salsa.debian.org/go-team/infra/pkg-go-tools/-/tree/master/config should also be updated, and the config should be changed to use debian/salsa-ci.yml by default instead of debian/gitlab-ci.yml by default, but that can and should be done only after this PR has been merged first and shipped in a dh-make-golang update.

…m CI

Instead of having both the Go team custom CI and Salsa CI, simply use
the default template with minimal customizations from
https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/recipes/salsa-ci.yml

This simplifies the CI and continues to give the same benefits as before,
as the Salsa CI pipeline jobs have made the custom Go team CI obsolete.
ottok added a commit to ottok/dh-make-golang that referenced this pull request May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant