Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: =?iso-8859-1?Q?I=F1aki?= Malerba Newsgroups: linux.debian.maint.python Subject: Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team repos Date: Mon, 19 Sep 2022 14:20:02 +0200 Message-ID: References: X-Original-To: Emanuele Rocca X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Sep 19 12:15:14 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-2 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MURPHY_DRUGS_REL7=0.2] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-Greylist: delayed 375 seconds by postgrey-1.36 at bendel; Mon, 19 Sep 2022 11:58:36 UTC Mail-Followup-To: Emanuele Rocca , debian-salsa-ci@alioth-lists.debian.net, debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/20312 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/YyhX6XljFwVANJfN@Randy Approved: robomod@news.nic.it Lines: 56 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-salsa-ci@alioth-lists.debian.net, debian-python@lists.debian.org X-Original-Date: Mon, 19 Sep 2022 13:52:09 +0200 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:14471 Hello Emanuele ! On Mon, Sep 19, 2022 at 12:51:00PM +0200, Emanuele Rocca wrote: > 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). That would be great ! Mass-enabling CI on groups might be something that you want to discuss with Salsa admins first. On previous occasions they pushed back on this kind of steep adoption due to the workload increase, but I'm not sure what's the stance right now on that matter. > > 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. One of the biggest issues we had when a team adopted the pipeline was DDOSing of the instance because of the multiple pipelines generated when pusing the .gitlab-ci.yml file to all the projects. If you're planning to do this, please: - Use the API and configure the 'CI/CD configuration file' project field, as you mentioned in the email. This won't generate a pipeline when configured but only on the next push. - If you need create the .gitlab-ci.yml file, please use the `ci.skip`[1] push option. Thanks, and good luck :) Iņaki 1_ https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd > > Thanks, > Emanuele > > [1] recipes/debian.yml@salsa-ci-team/pipeline > > -- > Debian-salsa-ci mailing list > Debian-salsa-ci@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-salsa-ci