On Aug 23, Theodore Ts'o <ty...@mit.edu> wrote: > 1) From a technical respective, what does Salsa CI buy me? Is it just Maybe different and more Debian-specific tests than the one that you are running elsewhere? They should all be documented here: https://salsa.debian.org/salsa-ci-team/pipeline/ .
> 2) If I'm already using Github's CI, and have autopkgtest, what are > the benefits for using Salsa CI? (Especially given the amount of Standardized Debian testing? > testing that I'm doing already, why should I spend more time enabling > Salsa CI?) The effort needed to do so is so small that the question really should be "why should I NOT spend a few seconds enabling Salsa CI?". > 3) What's the simple recipe for enable Salsa CI? salsa update_projects $NAMESPACE/$PROJECT \ --jobs yes --ci-config-path recipes/debian.yml@salsa-ci-team/pipeline (salsa(1) is part of devscripts) And then you can immediately schedule a new pipeline without having to push a new commit: https://salsa.debian.org/$NAMESPACE/$PROJECT/-/pipelines/new > 4) Where do the results for Salsa CI end up getting reported? https://salsa.debian.org/$NAMESPACE/$PROJECT/-/pipelines/, and you will also get emails for pass/fail transitions. -- ciao, Marco
signature.asc
Description: PGP signature
