Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #17035

Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead

From Otto Kekäläinen <otto@debian.org>
Newsgroups linux.debian.maint.python
Subject Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead
Date 2025-08-27 22:20 +0200
Message-ID <LouMG-aQ1V-19@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hi!

tldr;
Are people on the team fine with not using
recipes/debian.yml@salsa-ci-team/pipeline as the default setting in
future and using debian/salsa-ci.yml instead?

context:
I was looking at which of the Salsa CI jobs take longest and consume
most resources and stumbled across
https://salsa.debian.org/python-team/packages/graph-tool

The build uses more memory than available on a Salsa CI runner, and it
has never, and will never build. The reason it had CI running anyway
was that in the CI/CD configuration it had
`recipes/debian.yml@salsa-ci-team/pipeline`, which in turn was added
in all Python projects in an effort to enable CI to all packages.

I suggest a better practice would be to have as the CI/CD
configuration simply `debian/salsa-ci.yml` instead, so that the
pipeline runs only on Debian branches and starts running only after a
human added it there with intention and presumably that it actually
passed initially when CI was introduced.

I did this change now on the graph-tool project and also posted
https://salsa.debian.org/python-team/packages/graph-tool/-/merge_requests/1
to have the state of Salsa CI in the project documented.
- Otto

Back to linux.debian.maint.python | Previous | NextNext in thread | Find similar


Thread

Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Otto Kekäläinen <otto@debian.org> - 2025-08-27 22:20 +0200
  Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Andrey Rakhmatullin <wrar@debian.org> - 2025-08-27 22:30 +0200
      Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-08-27 22:50 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Carsten Schoenert <c.schoenert@t-online.de> - 2025-08-28 14:20 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Andrey Rakhmatullin <wrar@debian.org> - 2025-08-28 15:30 +0200
      Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-08-27 23:00 +0200
  Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-08-27 23:00 +0200
    Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Otto Kekäläinen <otto@debian.org> - 2025-09-09 02:40 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 03:20 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 03:40 +0200
      Re: Debian Python team: don't use  recipes/debian.yml@salsa-ci-team/pipeline, use debian/salsa-ci.yml instead Santiago Vila <sanvila@debian.org> - 2025-09-09 15:10 +0200
          Re: Debian Python team: don't use recipes/debian.yml@salsa-ci-team/pipeline,  use debian/salsa-ci.yml instead Soren Stoutner <soren@debian.org> - 2025-09-09 19:20 +0200

csiph-web