From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v1 4/6] CI: make test-artifacts branch/job customizable
Date: Mon, 23 Jun 2025 23:30:14 +0200 [thread overview]
Message-ID: <aFnHZnxBextHJRZy@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2506231401090.8066@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 4020 bytes --]
On Mon, Jun 23, 2025 at 02:04:36PM -0700, Stefano Stabellini wrote:
> On Mon, 23 Jun 2025, Marek Marczykowski-Górecki wrote:
> > Allow choosing which artifacts branch and job to use for Linux. This
> > allows running the same tests for different Linux versions, without
> > duplicating a lot of yaml sections.
>
> I just sent this reply:
> https://lore.kernel.org/xen-devel/alpine.DEB.2.22.394.2506231351060.8066@ubuntu-linux-20-04-desktop/
>
> You are answering my question: the goal is to allow much wider Linux
> versions testing? Because if not, I don't think there is much of a
> benefit.
Yes, the goal is to get wider Linux versions testing, including some
select "staging" Linux branches, not only frozen tags.
> Do you envision a bunch of jobs in automation/gitlab-ci/test.yaml that
> play with different LINUX_JOB_X86_64 / LINUX_JOB_ARM64 ? If so, we would
> need the corresponding jobs in test-artifacts.
See the cover letter (in which I forgot to CC you...).
The idea is to have separate pipelines (via a schedule) to test
different Linux branches, and each of them would select what Linux
branch is tested using those variables. For the LINUX_JOB_* variables it
would be mostly selecting between "frozen" Linux tag (for Xen standard
pipeline) and the "arbitrary git branch" one (for different Linux
versions). And then in the test-artifacts repo it can be either by
adding more jobs (as you suggests here), or more branches (all equal to
master) - each having a pipelines with different
LINUX_GIT_VERSION/LINUX_GIT_URL. In the latter case,
LINUX_ARTIFACTS_BRANCH would select which Linux build to use (+
LINUX_JOB_* set to linux-git-*).
> > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> > ---
> > I have considered common LINUX_JOB and then add architecture suffix, but
> > even now X86 and ARM use different jobs, so I made them separate.
> > ---
> > .gitlab-ci.yml | 9 +++++++++
> > automation/gitlab-ci/test.yaml | 8 ++++----
> > 2 files changed, 13 insertions(+), 4 deletions(-)
> >
> > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> > index 7974ac4e82bc..c1d92dc485e7 100644
> > --- a/.gitlab-ci.yml
> > +++ b/.gitlab-ci.yml
> > @@ -2,6 +2,15 @@ variables:
> > XEN_REGISTRY: registry.gitlab.com/xen-project/xen
> > SELECTED_JOBS_ONLY:
> > description: "Regex to select only some jobs, must be enclosed with /. For example /job1|job2/"
> > + LINUX_ARTIFACTS_BRANCH:
> > + description: "Branch in test-artifacts to use for Linux"
> > + value: master
> > + LINUX_JOB_X86_64:
> > + description: "Job name in test-artifacts to use for Linux x86_64"
> > + value: linux-6.12.34-x86_64
> > + LINUX_JOB_ARM64:
> > + description: "Job name in test-artifacts to use for Linux arm64"
> > + value: linux-6.6.86-arm64
> >
> > workflow:
> > name: "$CI_PIPELINE_SCHEDULE_DESCRIPTION"
> > diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> > index dc08488e76f4..9fd66fb6138d 100644
> > --- a/automation/gitlab-ci/test.yaml
> > +++ b/automation/gitlab-ci/test.yaml
> > @@ -9,8 +9,8 @@
> >
> > .arm64-test-needs: &arm64-test-needs
> > - project: xen-project/hardware/test-artifacts
> > - job: linux-6.6.86-arm64
> > - ref: master
> > + job: $LINUX_JOB_ARM64
> > + ref: $LINUX_ARTIFACTS_BRANCH
> > - project: xen-project/hardware/test-artifacts
> > job: alpine-3.18-arm64-rootfs
> > ref: master
> > @@ -21,8 +21,8 @@
> >
> > .x86-64-test-needs: &x86-64-test-needs
> > - project: xen-project/hardware/test-artifacts
> > - job: linux-6.12.34-x86_64
> > - ref: master
> > + job: $LINUX_JOB_X86_64
> > + ref: $LINUX_ARTIFACTS_BRANCH
> > - project: xen-project/hardware/test-artifacts
> > job: alpine-3.18-x86_64-rootfs
> > ref: master
> > --
> > git-series 0.9.1
> >
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-23 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:47 [PATCH v1 0/6] Add infrastructure for testing arbitrary Linux branch, and one more runner Marek Marczykowski-Górecki
2025-06-23 13:47 ` [PATCH v1 1/6] CI: Switch x86 tests to 6.12.34 kernel Marek Marczykowski-Górecki
2025-06-23 20:54 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 2/6] CI: add AMD Zen 4 HW runner Marek Marczykowski-Górecki
2025-06-23 13:47 ` [PATCH v1 3/6] CI: upload tests-junit.xml as a normal artifact too Marek Marczykowski-Górecki
2025-06-23 20:57 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 4/6] CI: make test-artifacts branch/job customizable Marek Marczykowski-Górecki
2025-06-23 21:04 ` Stefano Stabellini
2025-06-23 21:30 ` Marek Marczykowski-Górecki [this message]
2025-06-23 13:47 ` [PATCH v1 5/6] CI: use Alpine's network setup Marek Marczykowski-Górecki
2025-06-23 20:58 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 6/6] [DO NOT MERGE] CI: example how to use ssh to extract logs Marek Marczykowski-Górecki
2025-06-23 18:28 ` Demi Marie Obenour
2025-06-23 18:30 ` Marek Marczykowski-Górecki
2025-06-23 20:58 ` Stefano Stabellini
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=aFnHZnxBextHJRZy@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.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.