From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EBF06C04A95 for ; Wed, 28 Sep 2022 08:29:22 +0000 (UTC) Received: from localhost ([::1]:35260 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odSRV-0007zw-Sv for qemu-devel@archiver.kernel.org; Wed, 28 Sep 2022 04:29:21 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:39016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odRQV-0003dl-Qq for qemu-devel@nongnu.org; Wed, 28 Sep 2022 03:24:21 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:35979) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odRQT-0000vt-Pr for qemu-devel@nongnu.org; Wed, 28 Sep 2022 03:24:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664349853; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VvV2DsO/ypsAQZ4RgJWh+UeoVnT1H1iQFQ4v+FjoxUU=; b=Yw2Kh1deqEpCQmIcFwaJPI5kHP/1OGZNxvihBdC/fda+3Q/ApXr8l8J6+rTVCzm/ajI7qy ZS1aJqjPNxfEJrVB5bqr9h1TO6qV3zN+N4CoiiongjK52+GCbg8ljL0DJGy+thnfvSM2Pj A0VU/g/hY9WtnIeQ+YLN8ePSTeMdFLE= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-622-S-R0nk17PvuSfLSUaVSMZw-1; Wed, 28 Sep 2022 03:24:07 -0400 X-MC-Unique: S-R0nk17PvuSfLSUaVSMZw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4344B811E81; Wed, 28 Sep 2022 07:24:07 +0000 (UTC) Received: from redhat.com (unknown [10.33.36.68]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F1628140EBF5; Wed, 28 Sep 2022 07:24:05 +0000 (UTC) Date: Wed, 28 Sep 2022 08:24:03 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Thomas Huth Cc: Stefan Hajnoczi , QEMU Developers , Alex =?utf-8?Q?Benn=C3=A9e?= , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , Stefan Hajnoczi , Peter Maydell , Richard Henderson Subject: Re: Should we maybe move Cirrus-CI jobs away from Gitlab again? Message-ID: References: <285e1375-82c4-556d-54fa-abba6b8e8e77@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.6 (2022-06-05) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -21 X-Spam_score: -2.2 X-Spam_bar: -- X-Spam_report: (-2.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.082, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Sep 27, 2022 at 08:40:44PM +0200, Thomas Huth wrote: > On 27/09/2022 19.57, Daniel P. Berrangé wrote: > > On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote: > > > On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé wrote: > > > > > > > > On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefan Hajnoczi wrote: > > > > > On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote: > > > > > > now that Gitlab is giving us pressure on the amount of free CI minutes, I > > > > > > wonder whether we should maybe move the Cirrus-CI jobs out of the gitlab-CI > > > > > > dashboard again? We could add the jobs to our .cirrus-ci.yml file instead, > > > > > > like we did it in former times... > > > > > > > > > > > > Big advantage would be of course that the time for those jobs would not > > > > > > count in the Gitlab-CI minutes anymore. Disadvantage is of course that they > > > > > > do not show up in the gitlab-CI dashboard anymore, so there is no more > > > > > > e-mail notification about failed jobs, and you have to push to github, too, > > > > > > and finally check the results manually on cirrus-ci.com ... > > > > > > > > > > My understanding is that .gitlab-ci.d/cirrus.yml uses a GitLab CI job > > > > > to run the cirrus-run container image that forwards jobs to Cirrus-CI. > > > > > So GitLab CI resources are consumed waiting for Cirrus-CI to finish. > > > > > > > > > > This shouldn't affect gitlab.com/qemu-project where there are private > > > > > runners that do not consume GitLab CI minutes. > > > > > > > > > > Individual developers are affected though because they most likely > > > > > rely on the GitLab shared runner minutes quota. > > > > > > > > NB, none of the jobs should ever be run automatically anymore in > > > > QEMU CI pipelines. It always requires the maintainer to set the > > > > env var when pushing to git, to explicitly create a pipeline. > > > > You can then selectively start each individual job as desired. > > > > > > Cirrus CI is not automatically started when pushing to a personal > > > GitLab repo? If starting it requires manual action anyway then I think > > > nothing needs to be changed here. > > > > No pipeline at all is created unless you do > > > > git push -o ci.variable=QEMU_CI=1 > > > > that creates the pipeliune but doesn't run any jobs - they're manual > > start. > > Yes, sure, the jobs are not started automatically. But I *do* want to run > the jobs before sending pull requests - but since the gitlab-CI minutes are > now very limited, I'd like to avoid burning these minutes via gitlab and > start those jobs directly on cirrus-ci.com again. For that the jobs would > need to be moved to our .cirrus-ci.yml file again. We do need a better story for maintainers sending pull requests to have ability to run CI. We have 50+ jobs in the bujild stage of which the cirrus jobs are just 3 - removing the cirrus jobs won't make a difference to how quickly we run out of minutes if people try to run all of them. We need to define a much tighter minimalist set of recommended jobs to run. I believe that if QEMU joins the OSS program, then the forks of QEMU also benefit from a reduced cost factor for jobs they run, effectively giving you much higher CI quota > Well, maybe we could also have both, jobs via cirrus-run for those who want > to see them in their gitlab-CI dashboard, and via .cirrus-ci.yml for those > who want to avoid burning CI minutes on Gitlab. It's a little bit of > double-maintenance, but maybe acceptable? Key info about the jobs is in .gitlab-ci.d/cirrus/freebsd-12.vars which could be referenced from the cirrus-ci.yml to reduce duplication With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|