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: [TEST_ARTIFACTS PATCH v1 0/1] build: add x86_64 xen artifacts (argo)
Date: Thu, 24 Oct 2024 16:26:48 -0700	[thread overview]
Message-ID: <cover.1729809799.git.victorm.lira@amd.com> (raw)

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

The current configuration of Xen CI generates test binaries using "export"
jobs in every pipeline. This unecessarily uses a large amount of storage
and network traffic because artifacts are duplicated over each project and
branch that uses this configuration.

Instead, use a separate repository to store test binaries, then they can be
retrieved using GitLab CI built-in functionality. A test job can pull
binaries from another project job using the "needs" syntax. This will pull
from the most recent successful job on the specified branch. However, it
will not wait for a currently running job to finish and will instead pull
from previous jobs. This should not be a problem as we expect to change the
binaries only rarely.

Victor Lira (1):
  build: add x86_64 xen artifacts (argo)

 .gitlab-ci.yml                         | 50 ++++++++++++++++++++
 binaries/.gitignore                    |  3 ++
 images/Makefile                        | 20 ++++++++
 images/alpine/x86_64-build.dockerfile  | 31 +++++++++++++
 images/alpine/x86_64-rootfs.dockerfile |  4 ++
 scripts/x86_64-argo-linux.sh           | 63 ++++++++++++++++++++++++++
 scripts/x86_64-kernel-linux.sh         | 31 +++++++++++++
 scripts/x86_64-rootfs-alpine.sh        | 58 ++++++++++++++++++++++++
 8 files changed, 260 insertions(+)
 create mode 100644 .gitlab-ci.yml
 create mode 100644 binaries/.gitignore
 create mode 100644 images/Makefile
 create mode 100644 images/alpine/x86_64-build.dockerfile
 create mode 100644 images/alpine/x86_64-rootfs.dockerfile
 create mode 100755 scripts/x86_64-argo-linux.sh
 create mode 100755 scripts/x86_64-kernel-linux.sh
 create mode 100755 scripts/x86_64-rootfs-alpine.sh

--
2.25.1



             reply	other threads:[~2024-10-24 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 23:26 victorm.lira [this message]
2024-10-24 23:26 ` [TEST_ARTIFACTS PATCH v1 1/1] build: add x86_64 xen artifacts (argo) victorm.lira
2024-10-25  1:09   ` 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.1729809799.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.