Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Emanuele Rocca Newsgroups: linux.debian.maint.python Subject: Enabling salsa-ci on all Debian Python Team repos Date: Mon, 19 Sep 2022 12:50:01 +0200 Message-ID: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Sep 19 10:47:27 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.599 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: ACrzQf35LRLcYddJd2O/9t0jMRiz8Zdf64hEwUHdOhvzcuoPwecjyOeQ 4NxOt8KQTwwt4jkpT37A6InkEXskacY= X-Google-SMTP-Source: AMsMyM6Hqw0LUnFRbP+u2YWjawDvaoCdAzQWDGhJCOmd5uIi56+qIlkSRq77Nlvgj2JF3lvKRaVQWg== X-Received: by 2002:a17:907:a0c6:b0:77d:7ad3:d05f with SMTP id hw6-20020a170907a0c600b0077d7ad3d05fmr12312456ejc.734.1663584424882; Mon, 19 Sep 2022 03:47:04 -0700 (PDT) Sender: robomod@news.nic.it MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/20311 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/YyhJlIioRwRr7bAp@ariel Approved: robomod@news.nic.it Lines: 19 Organization: linux.* mail to news gateway X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Mon, 19 Sep 2022 12:51:00 +0200 X-Original-Message-ID: X-Original-Sender: Emanuele Rocca Xref: csiph.com linux.debian.maint.python:14470 Hello debian-salsa-ci and debian-python! I was wondering if it would make sense to enable CI/CD on Salsa for all projects owned by the Debian Python Team, or if there's any concern about scaling issues in terms of pipeline workers (or anything else really). For the past few days I've been enabling CI/CD on Salsa for various packages owned by the DPT. I've been doing this on a case-by-case basis: if the package I wanted to work on (for reasons unrelated to CI) did not have CI/CD yet, I'd add [1] as the pipeline configuration file and carry on with my work. Perhaps there's an opportunity to automate and getting wider CI usage. Thanks, Emanuele [1] recipes/debian.yml@salsa-ci-team/pipeline