All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/6] Clean up Gitlab yaml
Date: Thu, 10 Apr 2025 13:20:14 +0000	[thread overview]
Message-ID: <Z_fFjGRdQDNYQtfn@l14> (raw)
In-Reply-To: <20250410114628.2060072-3-andrew.cooper3@citrix.com>

On Thu, Apr 10, 2025 at 12:46:24PM +0100, Andrew Cooper wrote:
> Factor out the registry into a common location.  Drop the worflow name, as all
> it does is hide the commit message of the change that triggered the pipeline.
> List all the stages.  Set a default expiry of 1 month.
> 
> Note all the current jobs as legacy.  Their naming scheme needs changing, and
> we'll use this opportunity to switch formats too.  However, the artefacts need
> to stay using the old name until the final staging-* branch using them is
> phased out.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks,

-- 

Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech




  parent reply	other threads:[~2025-04-10 13:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 11:46 [PATCH TEST-ARTEFACTS v2 0/6] Cleanup and Linux ARM64 support Andrew Cooper
2025-04-10 11:46 ` [PATCH 1/6] Port containerise Andrew Cooper
2025-04-10 13:18   ` Anthony PERARD
2025-04-10 11:46 ` [PATCH 2/6] Clean up Gitlab yaml Andrew Cooper
2025-04-10 12:25   ` Marek Marczykowski-Górecki
2025-04-10 13:20   ` Anthony PERARD [this message]
2025-04-10 11:46 ` [PATCH 3/6] Adjust Linux build script to work with other major versions Andrew Cooper
2025-04-10 12:09   ` Marek Marczykowski-Górecki
2025-04-10 11:46 ` [PATCH 4/6] Factor our x86-isms in the linux build script Andrew Cooper
2025-04-10 11:46 ` [PATCH 5/6] Infrastructure for arm64 linux builds Andrew Cooper
     [not found]   ` <Z_fM44HXEnpwa8q6@l14>
2025-04-10 14:08     ` Andrew Cooper
2025-04-10 11:46 ` [PATCH 6/6] Linux builds for x86 and ARM64 Andrew Cooper
2025-04-10 14:03   ` 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=Z_fFjGRdQDNYQtfn@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.