[Debian-salsa-ci] Salsa CI usage stats (Re: I want to help)

[Otto Kekäläinen]

Hi!

> >> Alternatively, you could start getting familiar with Salsa-CI by using
> >> it first, before doing changes to the CI system itself. You could for
> >> example systematically review all top-100 source packages in Debian
> >> sorted by the installation base of them
> >> (https://popcon.debian.org/sourcemax/by_inst) and check if they are
> >> using Salsa-CI or not. For those that are hosted on salsa.debian.org,
> >> but not yet using Salsa-CI, you could submit a MR to activate
> >> Salsa-CI.
> > This is interesting. Do you know if there's a way to know the packages
> > inside a namespace/team run salsa-ci?
>
> Here's a perl script (there's a similar python library AFAIK, and
> possibly ruby too) that reports about things in the installer-team
> repos.
>
>   https://salsa.debian.org/installer-team/branch2repo/-/blob/main/scripts/salsa-control-ci-checker
>
> That script looks in each repo'debian/control file to see if there are
> any non-udeb packages, and also looks at the ci_config_path to see if
> it's set to vanilla branch2repo (which is only really appropriate for
> pure udeb packages), and reports the ones that are wrong.
>
> Seemed like it might be the sort of thing you're looing for.
>
> If you just want to know if they're using CI, you could look for
> ci_config_path being set, and if it is set to e.g. debian/salsa-ci.yml,
> you could also check if such a file exists.

Interesting. There are no inline comments but seems to be a Perl
script that looks into a single Salsa project (id 2655) and fetches
the debian/control and .gitlab-ci.yml file. We would need to have
something that scans the GitLab/Salsa API for pipeline runs and
results I presume.