From: Romain Naour <romain.naour@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] support/scripts/generate-gitlab-ci-yml: make it possible to test multiple defconfigs
Date: Thu, 30 Dec 2021 17:44:32 +0100 [thread overview]
Message-ID: <7e70f53d-e66f-607e-b8a7-853d25ffd19f@gmail.com> (raw)
In-Reply-To: <20211229143843.1271981-1-thomas.petazzoni@bootlin.com>
Hello Thomas,
Le 29/12/2021 à 15:38, Thomas Petazzoni a écrit :
> Already supported:
>
> - Pushing a branch called "<foo>-defconfigs" tests all defconfigs.
>
> - Pushing a branch called "<foo>-defconfig-<defconfig-name>" will
> test one particular defconfig
>
> This commit adds support for:
>
> - Pushing a branch called "<foo>-defconfigs-<pattern>" which will
> test all defconfigs whose name start with the pattern. For example
> "<foo>-defconfigs-qemu_" will test all Qemu defconfigs
I'm doing a shameless local hack in generate-gitlab-ci-yml to keep only qemu*
defconfig for testing in gitlab:
defconfigs=( $(cd configs; LC_ALL=C ls -1 qemu*_defconfig) )
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> Ideally, this should be documented in the Buildroot manual, but I'm
> not sure where it should be documented.
Probably a new chapter after "22.7. Using the run-tests framework".
"22.8. Testing using Buildroot's gitlab-ci"
> ---
> support/scripts/generate-gitlab-ci-yml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/support/scripts/generate-gitlab-ci-yml b/support/scripts/generate-gitlab-ci-yml
> index 8aaa456b03..3e0c68091b 100755
> --- a/support/scripts/generate-gitlab-ci-yml
> +++ b/support/scripts/generate-gitlab-ci-yml
> @@ -66,6 +66,11 @@ gen_tests() {
> (*-defconfigs)
> do_defconfigs=base
> ;;
> + (*-defconfigs-*)
> + pattern=$(echo ${CI_COMMIT_REF_NAME} | sed 's%[^\-]*-defconfigs-\(.*\)%\1%')
> + defconfigs=( $(cd configs; LC_ALL=C ls -1 | grep ^${pattern}) )
> + do_defconfigs=base
> + ;;
I'll use this patch next time I'll test qemu defconfig.
Best regards,
Romain
> (*-*_defconfig)
> defconfigs=( "${CI_COMMIT_REF_NAME##*-}" )
> do_defconfigs=base
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-30 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 14:38 [Buildroot] [PATCH] support/scripts/generate-gitlab-ci-yml: make it possible to test multiple defconfigs Thomas Petazzoni
2021-12-30 16:44 ` Romain Naour [this message]
2021-12-30 17:42 ` Yann E. MORIN
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=7e70f53d-e66f-607e-b8a7-853d25ffd19f@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@buildroot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox