All of lore.kernel.org
 help / color / mirror / Atom feed
From: <victorm.lira@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: "Victor Lira" <victorm.lira@amd.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	"Doug Goldstein" <cardoe@cardoe.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>
Subject: [RFC TEST_ARTIFACTS PATCH 0/2] artifacts: Initial commit
Date: Tue, 22 Oct 2024 19:53:31 -0700	[thread overview]
Message-ID: <cover.1729649255.git.victorm.lira@amd.com> (raw)

From: Victor Lira <victorm.lira@amd.com>

This patch series is a proof of concept that a separate repository can be
used to generate kernel, rootfs, and other commonly used binary artifacts,
and have Xen test jobs load these instead of generating them every run.

The current configuration of Xen CI generates these using "dummy" jobs
in every pipeline. This unecessarily uses a large amount of storage and
network traffic because artifacts are duplicated overprojects/branches.

Instead, use GitLab CI built-in functionality to retrieve them from a
separate repository using the "needs" keyword. The "needs:project" feature
is currently limited to 5 artifacts archives from external pipelines per
job, but web requests can be used if more are needed. It's preferable to
use this as opposed to just web requests since this doesn't requre modying
the any test scripts as long as the archive has the same directory
structure.

The example of a test artifacts repository:
https://gitlab.com/xen-project/people/victormlira/test-artifacts/-/pipelines/1508031895

The example of the use:
https://gitlab.com/xen-project/people/sstabellini/xen/-/pipelines/1508069266

Stefano Stabellini (1):
  Initial commit

--
2.25.1



             reply	other threads:[~2024-10-23  2:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  2:53 victorm.lira [this message]
2024-10-23  2:53 ` [RFC TEST_ARTIFACTS PATCH 1/2] artifacts: Initial commit victorm.lira
2024-10-23  2:53   ` [RFC XEN PATCH 2/2] automation: add xilinx test (linux argo) victorm.lira
2024-10-23  5:03     ` Stefano Stabellini
2024-10-23  4:57   ` [RFC TEST_ARTIFACTS PATCH 1/2] artifacts: Initial commit 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=cover.1729649255.git.victorm.lira@amd.com \
    --to=victorm.lira@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=marmarek@invisiblethingslab.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.