Path: csiph.com!1.us.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Julian Gilbey <julian@d-and-j.net>
Newsgroups: linux.debian.maint.python
Subject: Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team  repos
Date: Mon, 19 Sep 2022 17:10:01 +0200
Message-ID: <F7qzf-8EpT-7@gated-at.bofh.it>
References: <F7mvD-8Bun-5@gated-at.bofh.it> <F7nUK-8Cun-5@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Mon Sep 19 15:06:08 2022
Old-Return-Path: <julian@d-and-j.net>
X-Amavis-Spam-Status: No, score=-7 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, LDO_WHITELIST=-5, MURPHY_DRUGS_REL7=0.2] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -4.6
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/20313
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/YyiFLv3U2qbsS+VT@d-and-j.net
Approved: robomod@news.nic.it
Lines: 28
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Mon, 19 Sep 2022 16:05:18 +0100
X-Original-Message-ID: <YyiFLv3U2qbsS+VT@d-and-j.net>
X-Original-References: <YyhJlIioRwRr7bAp@ariel> <YyhX6XljFwVANJfN@Randy>
Xref: csiph.com linux.debian.maint.python:14472

On Mon, Sep 19, 2022 at 01:52:09PM +0200, Iņaki Malerba wrote:
> [...]
> > 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.

Indeed; setting the configuration file to
  recipes/debian.yml@salsa-ci-team/pipeline
will avoid any need to touch the actual repository.

> - If you need create the .gitlab-ci.yml file, please use the
>   `ci.skip`[1] push option.

And that should only be needed if the configuration is non-standard.

> Thanks, and good luck :)

Best wishes,

   Julian