From: Romain Naour <romain.naour@smile.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jugurtha BELKALEM <jugurtha.belkalem@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATH v2 1/1] docs/manual: add qemu defconfigs gitlab test
Date: Sat, 8 Jan 2022 11:56:54 +0100 [thread overview]
Message-ID: <90d1cd65-6cb7-d708-9b57-2089c5485d63@smile.fr> (raw)
In-Reply-To: <20200915165156.179380a9@windsurf.hq.k.grp>
Hello Thomas,
Le 15/09/2020 à 16:51, Thomas Petazzoni a écrit :
> On Tue, 15 Sep 2020 12:38:06 +0200
> Jugurtha BELKALEM <jugurtha.belkalem@smile.fr> wrote:
>
>> +=== Adding qemu defconfig gitlab test
>> +
>> +Buildroot provides a test script (support/scripts/boot-qemu-image.py)
>> +to validate all defconfigs under +board/qemu/. Every supported qemu
>> +architecture should append the comment : # qemu_ARCH_defconfig
>> +at the end of its command line entry in board/qemu/ARCH/readme.txt (for
>> +example aarch64-virt includes : # qemu_aarch64_virt_defconfig).
>> +Once a week, every defconfig is tested under gitlab's pipelines :
>> +* Launches a qemu instance.
>> +* Enters root credentials and checks if login shell is available.
>> +* Powers off the instance.
>> +The job fails if one of above steps returns unsuccessful status code.
>> +to trigger qemu defconfigs test jobs:
>> +
>> +---------------------
>> + $ git push gitlab HEAD:<name>_defconfig
>> +---------------------
>
> While I understand the idea of documenting this, I am wondering if the
> Buildroot manual is really the right place for this. Indeed, this bit
> of documentation is really only useful for the very specific/narrow use
> case of qemu defconfigs.
>
> Should this be in board/qemu/readme.txt ? I'm not sure.
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.
Best regards,
Romain
>
> Thomas
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 10:57 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 [this message]
2022-01-08 17:52 ` Thomas Petazzoni
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=90d1cd65-6cb7-d708-9b57-2089c5485d63@smile.fr \
--to=romain.naour@smile.fr \
--cc=buildroot@buildroot.org \
--cc=jugurtha.belkalem@smile.fr \
--cc=thomas.petazzoni@bootlin.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 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.