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

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

Re: Streamlining the use of Salsa CI on team packages

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

On Sun, 15 Sep 2019, Louis-Philippe Véronneau wrote:
> For step 1, I proposed we use the "Salsa Pipeline" [1], as I feel it is
> the most mature solution, has more contributors and has more features
> (including reprotest and piuparts). This option seems to have had the
> most support so far.

Ack. I also deployed this pipeline on 500 Kali packages at
https://gitlab.com/kalilinux/packages/
and it has been working relatively well. There are a couple
of remaining issues but the project is evolving quickly and I'm
confident that we can get past them.

One of the issue is related to the fact that the CI build does not bump
the version and it can conflict with the version in the archive and it
will often confuse piuparts.
https://salsa.debian.org/salsa-ci-team/pipeline/issues/78

The project is a bit lacking in terms of leadership/guidance and there are
pending issues that should have been resolved more quickly to avoid
confusion and better define the rules:
https://salsa.debian.org/salsa-ci-team/pipeline/issues/84
https://salsa.debian.org/salsa-ci-team/pipeline/issues/76
https://salsa.debian.org/salsa-ci-team/pipeline/issues/86

> For step 2, so far people seemed to agree that:
> 
> * having a standardised CI pipeline is a good idea
> * the CI should be used as a tool to help us improve our packages, and
> not be required to pass

On this, I disagree. The CI should pass, but it's perfectly OK to
disable some of the failing tests to make it pass. We want merge requests
to run the CI and we want them to succeed to prove that they are not
making the package regress compared to the current situation.

Consider that the package tracker is likely to display the CI status at
some point.

Note that for merge request, it won't really work until 
https://gitlab.com/gitlab-org/gitlab/issues/30242 gets fixed in GitLab.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

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

Thread

Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-05 07:50 +0200
  Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-12 17:00 +0200
  Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-13 23:10 +0200
    Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-15 04:20 +0200
      Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-16 02:20 +0200
      Re: Streamlining the use of Salsa CI on team packages Marcin Kulisz <debian@kulisz.net> - 2019-09-16 09:30 +0200
  Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-09-16 02:40 +0200
    Re: Streamlining the use of Salsa CI on team packages Raphael Hertzog <hertzog@debian.org> - 2019-09-17 10:10 +0200
    Re: Streamlining the use of Salsa CI on team packages Louis-Philippe Véronneau <pollo@debian.org> - 2019-10-12 01:40 +0200
    RE:Streamlining the use of Salsa CI on team packages PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2019-10-14 16:10 +0200
      Re: Streamlining the use of Salsa CI on team packages Peter Pentchev <roam@ringlet.net> - 2019-10-15 09:40 +0200

csiph-web