[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Golang team Salsa CI runner and documentation

On 24/11/24 09:43, Otto Kekäläinen wrote:

Hi!

Are Go team members interested in being able to run plain Salsa CI on
their packages?


If I am not mistaken, by plain salsa CI you mean this thing https://salsa.debian.org/salsa-ci-team/pipeline
right?

I think so. This DC there was a discussion of getting rid of the legacy go salsa CI since the
go world has moved from untagged repos to following good semver practices.

Here are the notes for your ref: https://salsa.debian.org/debconf-team/public/data/dc24/-/blob/main/etherpad/txt/152-go-team-bof.txt

I personally use salsa CI pipeline (not the go one) for a couple of end user apps that I maintain.


I have posted a Merge Request at
https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/2
for discussion.
Example of it being used:
https://salsa.debian.org/otto/golang-github-tomasen-fcgi-client/-/pipelines/751593

...

On Tue, 17 Sept 2024 at 01:16, Otto Kekäläinen <otto@debian.org> wrote:


Hi!

I noticed the Go team has docs for having your own Salsa CI runner:
https://go-team.pages.debian.net/ci.html

There are also Ansible scripts to deploy it at
https://salsa.debian.org/go-team/infra/provisioning/-/tree/master/ci-runner,
though the runner configuration is not fully identical to the docs.

Perhaps this practice of having team-runners would make sense for
other teams as well?

We recently added in Salsa CI the doc
https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/RUNNERS.md,
and I wanted to invite you to contribute to it in case you have best
practices to share or if somebody wants to refactor the Ansible script
you have and make it generic enough to be something we could recommend
for any team or DD to use across Debian, and potentially distributed
as a single file/directory from a centralized place.

- Otto
Reply to: