From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH test-artifacts v3 07/13] Support building arbitrary Linux branch/tag/commit
Date: Wed, 15 Apr 2026 13:17:44 +0000 [thread overview]
Message-ID: <ad-P9s8enOeHWFyL@l14> (raw)
In-Reply-To: <b616361a3464b221a342dab11cd21ca76454a957.1774999132.git-series.marmarek@invisiblethingslab.com>
On Wed, Apr 01, 2026 at 01:21:57AM +0200, Marek Marczykowski-Górecki wrote:
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 58f7571f5366..62b2a24e7faf 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -49,9 +53,13 @@ alpine-3.22-arm64-rootfs:
>
> linux-6.6.86-arm64:
> extends: .arm64-artifacts
> - script: ./scripts/build-linux.sh
> - variables:
> - LINUX_VERSION: 6.6.86
> + script: ./scripts/build-linux.sh "6.6.86"
Is it crazy to think we could grab the linux version from the job name?
:-D
linux-6.6.86-arm64:
script:
- linux_version="$CI_JOB_NAME"
- linux_version="${linux_version#linux-}"
- linux_version="${linux_version%%-*}"
- ./scripts/build-linux.sh "$linux_version"
That would avoid having a job building a version of linux that is
different than the expected one, which can happen easly when duplicating
an existing job for building a new version of linux.
> diff --git a/scripts/build-linux.sh b/scripts/build-linux.sh
> index cf0e744bd232..882bac2189a6 100755
> --- a/scripts/build-linux.sh
> +++ b/scripts/build-linux.sh
> @@ -1,5 +1,8 @@
> #!/usr/bin/env bash
>
> +LINUX_VERSION="$1"
> +LINUX_GIT_URL="$2"
> +
> if test -z "${LINUX_VERSION}"
With LINUX_VERSION been set just before, this test doesn't make sense
anymore, or the error message is wrong.
> then
> >&2 echo "LINUX_VERSION must be set"; exit 1
Thanks,
--
| Vates
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2026-04-15 13:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 23:21 [PATCH test-artifacts v3 00/13] Changes for several CI improvements Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 02/13] Switch Linux builds to use Alpine 3.22 container Marek Marczykowski-Górecki
2026-04-01 6:46 ` Orzel, Michal
2026-04-01 6:58 ` Marek Marczykowski-Górecki
2026-05-03 21:21 ` Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 04/13] Add linux-6.12.79-x86_64 Marek Marczykowski-Górecki
2026-04-15 11:56 ` Anthony PERARD
2026-04-15 12:27 ` Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 05/13] Enable CONFIG_USB_RTL8152 in kernel for hw12 runner Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 06/13] Include git in the ARM64 build container too Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 07/13] Support building arbitrary Linux branch/tag/commit Marek Marczykowski-Górecki
2026-04-15 13:17 ` Anthony PERARD [this message]
2026-03-31 23:21 ` [PATCH test-artifacts v3 08/13] Save Linux config to artifacts too Marek Marczykowski-Górecki
2026-03-31 23:21 ` [PATCH test-artifacts v3 09/13] Add trigger-test job, to run test on a Linux built from a branch/tag Marek Marczykowski-Górecki
2026-04-15 13:44 ` Anthony PERARD
2026-04-15 17:40 ` Marek Marczykowski-Górecki
2026-04-22 15:36 ` Anthony PERARD
2026-03-31 23:22 ` [PATCH test-artifacts v3 10/13] Add linux-stubdom dependencies Marek Marczykowski-Górecki
2026-03-31 23:22 ` [PATCH test-artifacts v3 11/13] Prepare grub for booting x86_64 HVM domU from a disk Marek Marczykowski-Górecki
2026-03-31 23:22 ` [PATCH test-artifacts v3 12/13] Prepare grub for booting x86_64 HVM domU from a cdrom Marek Marczykowski-Górecki
2026-03-31 23:22 ` [PATCH test-artifacts v3 13/13] Setup ssh access to test systems Marek Marczykowski-Górecki
2026-04-16 14:53 ` Anthony PERARD
2026-04-15 11:50 ` [PATCH test-artifacts v3 03/13] Add debian rootfs artifact Anthony PERARD
2026-04-15 17:59 ` Marek Marczykowski-Górecki
2026-04-27 15:12 ` Anthony PERARD
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=ad-P9s8enOeHWFyL@l14 \
--to=anthony.perard@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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.