From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] ci_build: Introduce REPRO_TARGETS_SET
Date: Thu, 23 May 2019 14:27:33 +0200 [thread overview]
Message-ID: <dcc95b99-36fc-df1a-ea5c-5eb9a8565a51@siemens.com> (raw)
In-Reply-To: <20190518111158.16539-2-mosipov@ilbers.de>
Hi Maxim,
On 18/05/2019 13.11, Maxim Yu. Osipov wrote:
> Use minimal targets set to test local apt repo caching feature
>
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> scripts/ci_build.sh | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> index ae9f5c9..9d370ac 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -34,6 +34,10 @@ TARGETS_SET="\
> # qemu-user-static of <= buster too old to build that
> # multiconfig:qemuarm64-buster:isar-image-base
>
> +REPRO_TARGETS_SET="\
> + multiconfig:qemuarm-stretch:isar-image-base \
> + multiconfig:qemuarm64-stretch:isar-image-base \
> + multiconfig:qemuamd64-stretch:isar-image-base"
What is probably missing here a
'multiconfig:qemu*-buster:isar-image-base' target.
At least after my current base-apt patchset it should be possible to
build stretch and buster in the same build environment.
Claudius
>
> show_help() {
> echo "This script builds the default Isar images."
> @@ -116,10 +120,15 @@ fi
>
> if [ -n "$REPRO_BUILD" ]; then
> # Enable use of cached base repository
> - bitbake $BB_ARGS -c cache_base_repo $TARGETS_SET
> + bitbake $BB_ARGS -c cache_base_repo $REPRO_TARGETS_SET
> while [ -e bitbake.sock ]; do sleep 1; done
> sudo rm -rf tmp
> sed -i -e 's/#ISAR_USE_CACHED_BASE_REPO ?= "1"/ISAR_USE_CACHED_BASE_REPO ?= "1"/g' conf/local.conf
> + bitbake $BB_ARGS $REPRO_TARGETS_SET
> + while [ -e bitbake.sock ]; do sleep 1; done
> + # Cleanup and disable use of cached base repository
> + sudo rm -rf tmp
> + sed -i -e 's/ISAR_USE_CACHED_BASE_REPO ?= "1"/#ISAR_USE_CACHED_BASE_REPO ?= "1"/g' conf/local.conf
> fi
>
> # Start build for the defined set of configurations
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-05-23 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 11:11 [PATCH 1/2] ci_build: Include de0-nano-soc into parallel fast build Maxim Yu. Osipov
2019-05-18 11:11 ` [PATCH 2/2] ci_build: Introduce REPRO_TARGETS_SET Maxim Yu. Osipov
2019-05-20 13:48 ` Maxim Yu. Osipov
2019-05-23 12:27 ` Claudius Heine [this message]
2019-05-23 12:34 ` Maxim Yu. Osipov
2019-05-23 12:38 ` Claudius Heine
2019-05-23 12:46 ` Maxim Yu. Osipov
2019-05-23 13:17 ` Claudius Heine
2019-05-20 13:47 ` [PATCH 1/2] ci_build: Include de0-nano-soc into parallel fast build Maxim Yu. Osipov
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=dcc95b99-36fc-df1a-ea5c-5eb9a8565a51@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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