All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Jugurtha BELKALEM <jugurtha.belkalem@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATH v2 1/1] docs/manual: add qemu defconfigs gitlab test
Date: Sat, 8 Jan 2022 18:52:12 +0100	[thread overview]
Message-ID: <20220108185212.49ba2aae@windsurf> (raw)
In-Reply-To: <90d1cd65-6cb7-d708-9b57-2089c5485d63@smile.fr>

Hello Romain,

On Sat, 8 Jan 2022 11:56:54 +0100
Romain Naour <romain.naour@smile.fr> wrote:

> Maybe the manual needs a new chapter about the gitlab-ci in general and document
> all pipeline trigger supported.
> 
> For a new qemu defconfigs, we need to take care of:
> 
> - define "# qemu_ARCH_defconfig" tag in the file board/qemu/ARCH/readme.txt
> 
> - Use board/qemu/post-image.sh post image script and provide the name of the
> defconfig as argument of this script:
>   BR2_ROOTFS_POST_IMAGE_SCRIPT="board/qemu/post-image.sh"
>   BR2_ROOTFS_POST_SCRIPT_ARGS="$(BR2_DEFCONFIG)"
> 
> - Enable host-qemu to use qemu built by Buildroot for the host:
>   BR2_PACKAGE_HOST_QEMU=y
>   BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE=y
> 
> Being in the manual would promote gitlab-ci testing with Qemu.

Yes, I agree! We need a single place in the chapter with all the Gitlab
CI details. Like the test-pkg integration, testing of defconfigs,
testing of runtime tests, etc.

I'll mark this patch as Changes Requested, because we don't want just a
section/chapter specifically for the qemu defconfig testing in Gitlab
CI, but a broader section;

Please note that Gitlab CI testing of runtime tests is already
documented in the manual, so it will have to be refactored.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-08 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 10:38 [Buildroot] [PATH v2 1/1] docs/manual: add qemu defconfigs gitlab test Jugurtha BELKALEM
2020-09-15 14:51 ` Thomas Petazzoni
2022-01-08 10:56   ` Romain Naour
2022-01-08 17:52     ` Thomas Petazzoni [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=20220108185212.49ba2aae@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=jugurtha.belkalem@smile.fr \
    --cc=romain.naour@smile.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.