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

[Santiago Ruano Rincón]

El 23/08/24 a las 16:00, Theodore Ts'o escribió:
> On Fri, Aug 23, 2024 at 03:08:11PM +0200, Marco d'Itri wrote:
> > > 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 at salsa-ci-team/pipeline
> 
> OK, more stupid questions.  What is "$NAMESPACE"?
> 
> And I thought I saw something about a debin/salsa-ci.yml file?
> 
> 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.

That is 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.

ACK.

And probably the reason why the salsa command doesn't appear there is
because of my preferred way to configure the pipeline in a package is
adding the debian/salsa-ci.yml file. The Gitlab setting makes
customisations more difficult, and more difficult for others that don't
have read access to those settings. (Yes, this is not what is written in
the documentation, and I probably should create MR to discuss it.)

If you have any other questions, don't hesitate to ask! :-)

 -- Santiago
-------------- 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/20240823/42e89d46/attachment.sig>