From: "Anthony PERARD" <anthony.perard@vates.tech>
To: xen-devel@lists.xenproject.org
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Doug Goldstein" <cardoe@cardoe.com>
Subject: [XEN PATCH v2 2/3] CI: Define XEN_REGISTRY variable
Date: Tue, 19 Nov 2024 10:15:27 +0000 [thread overview]
Message-ID: <20241119101449.49747-3-anthony.perard@vates.tech> (raw)
In-Reply-To: <20241119101449.49747-1-anthony.perard@vates.tech>
This allow to change the registry used for container in a single
place, and could be controlled via other mean.
Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
---
.gitlab-ci.yml | 3 +++
automation/gitlab-ci/build.yaml | 4 ++--
automation/gitlab-ci/test.yaml | 2 +-
3 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ef4484e09a..941e5822e8 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,3 +1,6 @@
+variables:
+ XEN_REGISTRY: registry.gitlab.com/xen-project/xen
+
workflow:
rules:
- if: $CI_COMMIT_BRANCH =~ /^(master|smoke|^coverity-tested\/.*|stable-.*)$/
diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index ce39b0ee21..1ca6764225 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -1,6 +1,6 @@
.build-tmpl: &build
stage: build
- image: registry.gitlab.com/xen-project/xen/${CONTAINER}
+ image: ${XEN_REGISTRY}/${CONTAINER}
script:
- ./automation/scripts/build 2>&1 | tee build.log
artifacts:
@@ -208,7 +208,7 @@
.yocto-test:
stage: build
- image: registry.gitlab.com/xen-project/xen/${CONTAINER}
+ image: ${XEN_REGISTRY}/${CONTAINER}
script:
- ./automation/build/yocto/build-yocto.sh -v --log-dir=./logs --xen-dir=`pwd` ${YOCTO_BOARD} ${YOCTO_OUTPUT}
variables:
diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
index ab5c8be0cd..1822e3ea5f 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -1,6 +1,6 @@
.test-jobs-common:
stage: test
- image: registry.gitlab.com/xen-project/xen/${CONTAINER}
+ image: ${XEN_REGISTRY}/${CONTAINER}
.arm64-test-needs: &arm64-test-needs
- alpine-3.18-arm64-rootfs-export
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2024-11-19 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 10:15 [XEN PATCH v2 0/3] CI: Allow automatic rebuild of rolling release containers Anthony PERARD
2024-11-19 10:15 ` [XEN PATCH v2 1/3] CI: Remove deprecated "only:variables" in favor of "rules:if" Anthony PERARD
2024-11-19 10:15 ` Anthony PERARD [this message]
2024-11-19 10:15 ` [XEN PATCH v2 3/3] CI: New stage "containers" to rebuild some containers Anthony PERARD
2024-11-19 21:47 ` Stefano Stabellini
2024-11-20 10:36 ` 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=20241119101449.49747-3-anthony.perard@vates.tech \
--to=anthony.perard@vates.tech \
--cc=andrew.cooper3@citrix.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.