From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Michal Orzel" <michal.orzel@amd.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [PATCH 4/8] Clean up Gitlab yaml
Date: Thu, 10 Apr 2025 10:07:40 +0000 [thread overview]
Message-ID: <Z_eYagfQ8vlMYenK@l14> (raw)
In-Reply-To: <20250409163702.2037301-5-andrew.cooper3@citrix.com>
On Wed, Apr 09, 2025 at 05:36:58PM +0100, Andrew Cooper wrote:
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 36ec6a7e1ee5..5a0a853e551d 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -1,12 +1,19 @@
> +variables:
> + REGISTRY: registry.gitlab.com/xen-project/hardware/test-artifacts
Did you consider naming that variable XEN_REGISTRY like in the xen.git
repo? REGISTRY is a fine name too.
> +
> workflow:
> - name: "xen test artifacts"
> + name: "Xen test artifacts"
Isn't this a very useless workflow:name? Can I suggest to remove it
instead? I mean, currently, all pipeline appear to do the same thing:
https://gitlab.com/xen-project/hardware/test-artifacts/-/pipelines
Without "workflow:name" set, the default name will be the subject of the
top commit.
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2025-04-10 10:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 16:36 [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support Andrew Cooper
2025-04-09 16:36 ` [PATCH 1/8] Consistently use DOCKER_CMD in makefiles Andrew Cooper
2025-04-09 16:36 ` [PATCH 2/8] Port containerise Andrew Cooper
2025-04-10 9:33 ` Anthony PERARD
2025-04-10 9:35 ` Andrew Cooper
2025-04-09 16:36 ` [PATCH 3/8] Fix container user setup Andrew Cooper
2025-04-10 9:41 ` Anthony PERARD
2025-04-09 16:36 ` [PATCH 4/8] Clean up Gitlab yaml Andrew Cooper
2025-04-09 17:15 ` Marek Marczykowski-Górecki
2025-04-10 9:38 ` Andrew Cooper
2025-04-10 10:07 ` Anthony PERARD [this message]
2025-04-10 10:11 ` Andrew Cooper
[not found] ` <Z_jid7eTY7EPIoWu@l14>
2025-04-11 9:45 ` Andrew Cooper
2025-04-09 16:36 ` [PATCH 5/8] Adjust Linux build script to work with other major versions Andrew Cooper
2025-04-09 16:57 ` Marek Marczykowski-Górecki
2025-04-09 17:18 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 6/8] Factor our x86-isms in the linux build script Andrew Cooper
2025-04-09 17:05 ` Marek Marczykowski-Górecki
2025-04-09 22:59 ` Marek Marczykowski-Górecki
2025-04-09 23:04 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 7/8] Infrastructure for arm64 linux builds Andrew Cooper
2025-04-09 17:11 ` Marek Marczykowski-Górecki
2025-04-09 17:15 ` Andrew Cooper
2025-04-10 10:41 ` Andrew Cooper
2025-04-10 10:57 ` Andrew Cooper
2025-04-10 12:21 ` Marek Marczykowski-Górecki
2025-04-10 9:59 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 8/8] Linux 6.6.86 for x86 and arm64 Andrew Cooper
2025-04-09 17:01 ` [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support Andrew Cooper
2025-04-10 0:09 ` Jason Andryuk
2025-04-10 9:17 ` Andrew Cooper
2025-04-10 18:20 ` Alejandro Vallejo
2025-04-10 18:28 ` Alejandro Vallejo
2025-04-10 19:50 ` [RFC PATCH] x86/xen: Fix PVH dom0 xen_hypercall detection Jason Andryuk
2025-04-10 21:49 ` Andrew Cooper
2025-04-11 11:35 ` Ard Biesheuvel
2025-04-11 14:28 ` Jason Andryuk
2025-04-11 15:32 ` Ard Biesheuvel
2025-04-11 12:46 ` Alejandro Vallejo
2025-04-11 13:08 ` Jan Beulich
2025-04-11 14:10 ` Alejandro Vallejo
2025-04-18 10:58 ` [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support David Woodhouse
2025-04-10 21:16 ` Jason Andryuk
2025-04-10 21:50 ` Jason Andryuk
2025-04-11 12:41 ` Alejandro Vallejo
2025-04-10 9:32 ` Jürgen Groß
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=Z_eYagfQ8vlMYenK@l14 \
--to=anthony.perard@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=michal.orzel@amd.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.