public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] ci_build: Introduce REPRO_TARGETS_SET
Date: Mon, 20 May 2019 15:48:22 +0200	[thread overview]
Message-ID: <d7787b83-4d7e-0368-2f89-35bd5e65aebf@ilbers.de> (raw)
In-Reply-To: <20190518111158.16539-2-mosipov@ilbers.de>

On 5/18/19 1:11 PM, Maxim Yu. Osipov wrote:
> Use minimal targets set to test local apt repo caching feature

Applied to the 'next'.

> 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"
>   
>   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
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

  reply	other threads:[~2019-05-20 13:48 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 [this message]
2019-05-23 12:27   ` Claudius Heine
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=d7787b83-4d7e-0368-2f89-35bd5e65aebf@ilbers.de \
    --to=mosipov@ilbers.de \
    --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