From: Thomas Huth <thuth@redhat.com>
To: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Should we maybe move Cirrus-CI jobs away from Gitlab again?
Date: Tue, 27 Sep 2022 10:22:04 +0200 [thread overview]
Message-ID: <285e1375-82c4-556d-54fa-abba6b8e8e77@redhat.com> (raw)
Hi all,
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 ...
Opinions?
Thomas
next reply other threads:[~2022-09-27 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 8:22 Thomas Huth [this message]
2022-09-27 15:44 ` Should we maybe move Cirrus-CI jobs away from Gitlab again? Stefan Hajnoczi
2022-09-27 15:54 ` Daniel P. Berrangé
2022-09-27 17:36 ` Stefan Hajnoczi
2022-09-27 17:57 ` Daniel P. Berrangé
2022-09-27 18:40 ` Thomas Huth
2022-09-27 18:47 ` Stefan Hajnoczi
2022-09-27 19:04 ` Thomas Huth
2022-09-27 19:10 ` Stefan Hajnoczi
2022-09-28 6:32 ` Thomas Huth
2022-09-28 7:10 ` Daniel P. Berrangé
2022-09-28 7:24 ` Daniel P. Berrangé
2022-09-28 12:27 ` Alex Bennée
2022-09-28 12:56 ` Stefan Hajnoczi
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=285e1375-82c4-556d-54fa-abba6b8e8e77@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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).