From: Eldon Stegall <eldon-qemu@eldondev.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
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 Mar 2023 05:53:28 +0000 [thread overview]
Message-ID: <ZBvpWMguR89kfZDG@invalid> (raw)
In-Reply-To: <ZBnd4/UTH6CD5vx7@redhat.com>
On Tue, Mar 21, 2023 at 04:40:03PM +0000, Daniel P. Berrangé wrote:
> 3 weeks later... Any progress on getting Red Hat to assign someone to
> setup Azure for our CI ?
I have the physical machine that we have offered to host for CI set up
with a recent version of fcos.
It isn't yet running a gitlab worker because I don't believe I have
access to create a gitlab worker token for the QEMU project. If creating
such a token is too much hassle, I could simple run the gitlab worker
against my fork in my gitlab account, and give full access to my repo to
the QEMU maintainers, so they could push to trigger jobs.
If you want someone to get the gitlab kubernetes operator set up in AKS,
I ended up getting a CKA cert a few years ago while working on an
operator. I could probably devote some time to get that going.
If any of this sounds appealing, let me know.
Thanks,
Eldon
next prev parent reply other threads:[~2023-03-23 5:53 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
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 [this message]
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=ZBvpWMguR89kfZDG@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 \
--cc=stefanha@gmail.com \
/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).