From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/8] CI rework of gitlab fast job
Date: Sun, 2 Apr 2023 21:13:47 +0200 [thread overview]
Message-ID: <ZCnT66Qalh0kxmUm@ilbers.de> (raw)
In-Reply-To: <Y8FZUiZ1Yk3KqguI@ilbers.de>
On 2023-01-13 14:14, Baurzhan Ismagulov wrote:
> * The maintainer CI provides test status and build control on a publicly
> accessible, easily scalable infrastructure.
FWIW, we've started with https://gitlab.isar-build.org/ in test mode. Please
report issues. The current low-performance runner will be replaced with a
better machine. We'll continue working on testing improvements.
With kind regards,
Baurzhan
prev parent reply other threads:[~2023-04-02 19:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 12:17 Henning Schild
2023-01-10 12:17 ` [PATCH 1/8] CI: move to avocado to 99.0 Henning Schild
2023-01-10 12:17 ` [PATCH 2/8] CI: fix shell coding style Henning Schild
2023-01-10 12:17 ` [PATCH 3/8] CI: install qemu-system when qemu testing is requested Henning Schild
2023-01-10 12:17 ` [PATCH 4/8] testsuite: remove Ccache test from "fast" set Henning Schild
2023-01-10 12:38 ` Jan Kiszka
2023-01-10 12:17 ` [PATCH 5/8] testsuite: remove Sdk " Henning Schild
2023-01-10 12:38 ` Jan Kiszka
2023-01-10 15:44 ` Henning Schild
2023-01-10 12:17 ` [PATCH 6/8] testsuite: remove ContainerImage " Henning Schild
2023-01-10 12:17 ` [PATCH 7/8] testsuite: remove ContainerSdk " Henning Schild
2023-01-10 12:17 ` [PATCH 8/8] testsuite: remove Sstate " Henning Schild
2023-01-10 12:24 ` [PATCH 0/8] CI rework of gitlab fast job Henning Schild
2023-01-12 12:23 ` Baurzhan Ismagulov
2023-01-12 15:12 ` Henning Schild
2023-01-12 15:20 ` Baurzhan Ismagulov
2023-01-12 23:43 ` Henning Schild
2023-01-13 4:34 ` Moessbauer, Felix
2023-01-13 13:14 ` Baurzhan Ismagulov
2023-01-13 17:14 ` Henning Schild
2023-01-14 14:40 ` Baurzhan Ismagulov
2023-01-23 8:26 ` Henning Schild
2023-04-02 19:13 ` Baurzhan Ismagulov [this message]
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=ZCnT66Qalh0kxmUm@ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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