From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] ci: Allow to define DISTRO_APT_PREMIRRORS in build environment
Date: Thu, 12 Aug 2021 11:22:16 +0200 [thread overview]
Message-ID: <5c54f4e2-8794-7e00-f131-45487867f9f7@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
This can be helpful to direct away from http://deb.debian.org where it
is in conflict with local network conditions.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
A surrender to our IT infrastructure. But maybe we are not alone. In
fact, I heard deb.debian.org is also not very fast behind the Great
Firewall.
.gitlab-ci.yml | 1 +
scripts/ci_build.sh | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 7fc1612..c91a997 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -10,6 +10,7 @@ variables:
- export https_proxy=$HTTPS_PROXY
- export ftp_proxy=$FTP_PROXY
- export no_proxy=$NO_PROXY
+ - export DISTRO_APT_PREMIRRORS=$DISTRO_APT_PREMIRRORS
artifacts:
name: "logs-$CI_JOB_ID"
paths:
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index a2895f6..a4aa74e 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -168,6 +168,10 @@ ISAR_ENABLE_COMPAT_ARCH_debian-stretch_amd64 = "0"
IMAGE_INSTALL += "kselftest"
EOF
+if [ -n "$DISTRO_APT_PREMIRRORS" ]; then
+ echo "DISTRO_APT_PREMIRRORS = \"$DISTRO_APT_PREMIRRORS\"" >> conf/local.conf
+fi
+
if [ -n "$CROSS_BUILD" ]; then
sed -i -e 's/ISAR_CROSS_COMPILE ?= "0"/ISAR_CROSS_COMPILE ?= "1"/g' conf/local.conf
fi
--
2.31.1
next reply other threads:[~2021-08-12 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 9:22 Jan Kiszka [this message]
2021-08-26 8:56 ` Anton Mikanovich
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=5c54f4e2-8794-7e00-f131-45487867f9f7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox