qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eldon Stegall <eldon-qemu@eldondev.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Ben Dooks <qemu@ben.fluff.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: out of CI pipeline minutes again
Date: Thu, 23 Feb 2023 22:11:11 +0000	[thread overview]
Message-ID: <Y/fkf3Cya1NOopQA@invalid> (raw)
In-Reply-To: <Y/eHLCKcdYk0V4Tt@redhat.com>

On Thu, Feb 23, 2023 at 03:33:00PM +0000, Daniel P. Berrangé wrote:
> IIUC, we already have available compute resources from a couple of
> sources we could put into service. The main issue is someone to
> actually configure them to act as runners *and* maintain their
> operation indefinitely going forward. The sysadmin problem is
> what made/makes gitlab's shared runners so incredibly appealing.

Hello,

I would like to do this, but the path to contribute in this way isn't clear to
me at this moment. I made it as far as creating a GitLab fork of QEMU, and then
attempting to create a merge request from my branch in order to test the GitLab
runner I have provisioned. Not having previously tried to contribute via
GitLab, I was a bit stymied that it is not even possibly to create a merge
request unless I am a member of the project? I clicked a button to request
access.  

Alex's plan from last month sounds feasible:
 
 - provisioning scripts in scripts/ci/setup (if existing not already 
 good enough) 
 - tweak to handle multiple runner instances (or more -j on the build) 
 - changes to .gitlab-ci.d/ so we can use those machines while keeping 
 ability to run on shared runners for those outside the project 

Daniel, you pointed out the importance of reproducibility, and thus the
use of the two-step process, build-docker, and then test-in-docker, so it
seems that only docker and the gitlab agent would be strong requirements for
running the jobs?

I feel like the greatest win for this would be to at least host the
cirrus-run jobs on a dedicated runner because the machine seems to
simply be burning double minutes until the cirrus job is complete, so I
would expect the GitLab runner requirements for those jobs to be low?

If there are some other steps that I should take to contribute in this
capacity, please let me know.

Maybe I could send a patch to tag cirrus jobs in the same way that the
s390x jobs are currently tagged, so that we could run those separately?

Thanks,
Eldon


  reply	other threads:[~2023-02-23 22:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 12:56 out of CI pipeline minutes again Peter Maydell
2023-02-23 13:46 ` Thomas Huth
2023-02-23 14:14   ` Daniel P. Berrangé
2023-02-23 14:15   ` Warner Losh
2023-02-23 15:00     ` Daniel P. Berrangé
2023-02-23 15:28 ` Ben Dooks
2023-02-23 15:33   ` Daniel P. Berrangé
2023-02-23 22:11     ` Eldon Stegall [this message]
2023-02-24  9:16       ` Gerd Hoffmann
2023-02-24 14:07       ` Alex Bennée
2023-02-27 16:59       ` Daniel P. Berrangé
2023-02-27 17:43         ` Stefan Hajnoczi
2023-03-01  4:51           ` Eldon Stegall
2023-03-01  9:53             ` Alex Bennée
2023-03-21 16:40           ` Daniel P. Berrangé
2023-03-23  5:53             ` Eldon Stegall
2023-03-23  9:05               ` Alex Bennée
2023-03-23  9:18             ` Paolo Bonzini
2023-02-24  9:54     ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y/fkf3Cya1NOopQA@invalid \
    --to=eldon-qemu@eldondev.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@ben.fluff.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).