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

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

Re: Enabling salsa-ci on all Debian Python Team repos

Show all headers | View raw

Hello Emanuele,

Am 21.09.22 um 12:01 schrieb Emanuele Rocca:
> Well but that's the whole point of automated testing. There's no *need*
> to do it locally if it's already done by Salsa for you. What is already
> automated and working pretty well is:
> 
> - amd64 build
> - i386 build
> - source build
> - autopkgtest
> - blhc
> - lintian
> - piuparts
> - reprotest
> - arm64 crossbuild
> 
> That's a pretty time consuming list of things to go through for a human!

sure, that's a killer argument that I can't really argue against. But 
that is not the point for me.

For all these checks we already have existing infrastructure, running 
the same also by a pipeline job isn't helping at all if it's not clear 
how to handle the fallout (we already mostly have seen in other places 
too!).

As Sandro and Arnaud have pointed out it's probably mostly a matter of 
the workflow for a package upload. And for me the CI pipeline stuff 
right now doesn't fit really into the package upload workflow that is 
typically used.

Using the CI stuff in your own namespace is perfectly fine and I'm using 
this option from time to time. But I use there also the possibility to 
do heavily force pushing to not blow up the git tree with dozens of 
Fixup commits! In the 'official' git tree this is a no go of course.

Nobody is perfect and even every Python package will have it's own small 
differences in between. As long as we don't have *one* Debian way to 
build packages and a helpful way to deal with breakage in any of the 
test runs it will always be a waste of time an energy to run for all 
packages a CI run at all times!

If the decision is to do this step I will simply need to ignore any 
errors that are not RC.

> The only work left to be done on your machine is a binary build to see
> if the packages look good, perhaps some specific manual testing [1],
> source build and upload. Isn't that better?

I do all package built locally as a all/any build run.
As written above and trying to say, I like atomic git commits that are 
doing things "correct" and by looking at the commit it's clear why this 
commit was done.
I have to "fight" enough on my day job with my colleagues as they do git 
mostly using committing every forward and backward steps with no clean 
up locally finally before pushing their stuff and so I need to spend a 
lot of time to get the changes and their basically meaning. You would 
end up the same in the packages here as people would commit again and 
again to fix up the packages.

I stand on my thinking, it's not helpful to enable a global CI for all 
packages. Doing this from case to case is absolutely fine to me.

Arnaud Ferraris has written about the usage of a CI option in Debian 
Mobile etc.
His writing is affirming me as I see and have the same experience within 
the PureOS ecosystem. People work there the same as I did describe, 
package are prepared in the local namespace and if the CI is running 
there successfully then a push to the team namespace is done.

-- 
Regards
Carsten

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-19 12:50 +0200
  Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team  repos Iñaki Malerba <ina@malerba.space> - 2022-09-19 14:20 +0200
    Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team  repos Julian Gilbey <julian@d-and-j.net> - 2022-09-19 17:10 +0200
  Re: Enabling salsa-ci on all Debian Python Team repos Louis-Philippe Véronneau <pollo@debian.org> - 2022-09-19 19:20 +0200
  Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-19 20:20 +0200
    Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-20 10:40 +0200
      Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-20 14:40 +0200
        Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-20 16:20 +0200
          Re: Enabling salsa-ci on all Debian Python Team repos Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-20 17:40 +0200
            Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-20 21:20 +0200
              Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-21 12:20 +0200
                Re: Enabling salsa-ci on all Debian Python Team repos Brian May <brian@linuxpenguins.xyz> - 2022-09-23 01:10 +0200
            Re: Enabling salsa-ci on all Debian Python Team repos Emanuele Rocca <ema@debian.org> - 2022-09-21 12:00 +0200
              Re: Enabling salsa-ci on all Debian Python Team repos Samuel Thibault <sthibault@debian.org> - 2022-09-21 12:40 +0200
              Re: Enabling salsa-ci on all Debian Python Team repos Sandro Tosi <morph@debian.org> - 2022-09-23 04:40 +0200
              Re: Enabling salsa-ci on all Debian Python Team repos Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-23 07:10 +0200
                Re: Enabling salsa-ci on all Debian Python Team repos Stefano Rivera <stefanor@debian.org> - 2022-09-23 08:30 +0200
                Re: Enabling salsa-ci on all Debian Python Team repos Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2022-09-23 09:00 +0200
            Re: Enabling salsa-ci on all Debian Python Team repos Arnaud Ferraris <aferraris@debian.org> - 2022-09-21 13:20 +0200

csiph-web