[Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

[Marco d'Itri]

On Aug 23, Theodore Ts'o <tytso at mit.edu> wrote:

> > salsa update_projects $NAMESPACE/$PROJECT \
> >   --jobs yes --ci-config-path recipes/debian.yml at salsa-ci-team/pipeline
> 
> OK, more stupid questions.  What is "$NAMESPACE"?
Whatever you see after "salsa.debian.org/" in the URL.

> And I thought I saw something about a debin/salsa-ci.yml file?
You do not need one, if your pipeline does not need any customization.
You can always add it later and change the path with salsa(1) or in the 
Salsa UI.

> And is this web page authoratative?  Or just a false search positive?
> 
>     https://salsa.debian.org/salsa-ci-team/pipeline#basic-use
> 
> It doesn't mention the "salsa" command at all, but maybe that isn't
> the right web page.  This goes back to my observation that it would be
> helpful if there was better documentation to make life easier for
> package maintainers.
It is authoritative, but apparently I was better than the actual 
CI maintainers at figuring out the simplest possibile recipe. :-)

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-salsa-ci/attachments/20240824/ae48492c/attachment.sig>