public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/8] CI rework of gitlab fast job
Date: Tue, 10 Jan 2023 13:24:04 +0100	[thread overview]
Message-ID: <20230110132404.64e4d43a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230110121748.14917-1-henning.schild@siemens.com>

I did not dare touching any of this for a very long time. But we have
reached a state where the CI is just a better room heater and not
meaningful, at least when done with gitlab and running the fast.

There is much to be improved, this is just a start. It is tested on our
gitlab and we save about 1.5h per run while we now vm-test all images
we build.

Henning

Am Tue, 10 Jan 2023 13:17:40 +0100
schrieb Henning Schild <henning.schild@siemens.com>:

> This series contains some changes to the CI as done on gitlab but also
> affects testing in general. The main idea is to run qemu basically
> every time we build an image (only fast for gitlab at the moment), so
> we do not just build it without testing.
> On the way i also improved shell style and removed some tests from the
> fast set, since they seem more advanced and just waste time on "fast"
> 
> Henning Schild (8):
>   CI: move to avocado to 99.0
>   CI: fix shell coding style
>   CI: install qemu-system when qemu testing is requested
>   testsuite: remove Ccache test from "fast" set
>   testsuite: remove Sdk test from "fast" set
>   testsuite: remove ContainerImage test from "fast" set
>   testsuite: remove ContainerSdk test from "fast" set
>   testsuite: remove Sstate test from "fast" set
> 
>  .gitlab-ci.yml      |  2 +-
>  scripts/ci_build.sh | 26 ++++++++++++++++----------
>  testsuite/citest.py | 10 +++++-----
>  3 files changed, 22 insertions(+), 16 deletions(-)
> 


  parent reply	other threads:[~2023-01-10 12:24 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 ` Henning Schild [this message]
2023-01-12 12:23 ` [PATCH 0/8] CI rework of gitlab fast job 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

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=20230110132404.64e4d43a@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --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