Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod From: Raphael Hertzog Newsgroups: linux.debian.maint.python Subject: Re: Streamlining the use of Salsa CI on team packages Date: Tue, 17 Sep 2019 10:10:01 +0200 Message-ID: References: X-Original-To: Louis-Philippe =?utf-8?Q?V=C3=A9ronneau?= X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Sep 17 08:00:15 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.751 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no Mail-Followup-To: Raphael Hertzog , Louis-Philippe =?utf-8?Q?V=C3=A9ronneau?= , debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Virus-Status: Clean X-Mailing-List: archive/latest/17366 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190917075959.GD18623@home.ouaza.com Approved: robomod@news.nic.it Lines: 73 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Tue, 17 Sep 2019 09:59:59 +0200 X-Original-Message-ID: <20190917075959.GD18623@home.ouaza.com> X-Original-References: <3429cc8e-87d4-facc-870d-1e664fe0779f@debian.org> Xref: csiph.com linux.debian.maint.python:11829 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Sun, 15 Sep 2019, Louis-Philippe V=C3=A9ronneau 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: >=20 > * 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=20 https://gitlab.com/gitlab-org/gitlab/issues/30242 gets fixed in GitLab. Cheers, --=20 Rapha=C3=ABl Hertzog =E2=97=88 Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/ --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Signed by Raphael Hertzog iQEzBAABCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl2Akn4ACgkQA4gdq+vC mrlmlggAsVK5A+DJ7yyxJQMQu5k+5FPekWHeoJcNKJvRQRFtUooZjFCrzB7/k08n 9u5CM0PZ6NYekh718BwTYOyXScQtScoceFv7S093p4dV38ST7ltCQZlIH6b/0ADc tpPDDpUrAZMDTYFl1TMO8QuUb2+PC/s2ZHj7mIJ8z5CLFDQp08xyLuAlHNg+OLDU Lc8o89OdyEH+of0zsjCP9GGUXAfbuzWxWhgl/gIl/GqZWEu4fKBkfitD/Kf0MvH7 R6oR/XEKugIuE7rxt4UXxLKXzdOIPi6cDd1kOWm2E5g6YM1+dlfh7Z1hBZuKvR+n a94eXCl7xkPMXSW8OvBsnmGXQTagjw== =4/aw -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--