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: [PATCH v2 1/2] ci: test rebuilding "hello"
Date: Tue, 19 Feb 2019 07:37:35 +0100	[thread overview]
Message-ID: <20190219063736.26836-2-mosipov@ilbers.de> (raw)
In-Reply-To: <20190219063736.26836-1-mosipov@ilbers.de>

From: Henning Schild <henning.schild@siemens.com>

This patch adds the rebuilding of "hello" to one distro that does
not get rebuild from the cache. The recipe uses a feature which
currently does not work for the caching case.

Once we can cache "apt://" URIs the package should probably move to all
tests.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 scripts/ci_build.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index bcc7545..b896f84 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -122,6 +122,11 @@ if [ -n "$REPRO_BUILD" ]; then
     sed -i -e 's/#ISAR_USE_CACHED_BASE_REPO ?= "1"/ISAR_USE_CACHED_BASE_REPO ?= "1"/g' conf/local.conf
 fi
 
+# "debian-buster" is currently not rebuild from the cache and the package
+# "hello" currently does not support being rebuild from the cache
+# so this distro is a good place to at least test the regular build
+echo "IMAGE_INSTALL_debian-buster += \"hello\"" >> conf/local.conf
+
 # Start build for the defined set of configurations
 bitbake $BB_ARGS $TARGETS_SET
 
-- 
2.11.0


  reply	other threads:[~2019-02-19  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  6:37 [PATCH v2 0/2] test rebuilding hello series Maxim Yu. Osipov
2019-02-19  6:37 ` Maxim Yu. Osipov [this message]
2019-02-19  6:37 ` [PATCH v2 2/2] ci: move IMAGE_INSTALL from config to ci script Maxim Yu. Osipov
2019-02-19 15:20 ` [PATCH v2 0/2] test rebuilding hello series Henning Schild
2019-02-20 13:53   ` Maxim Yu. Osipov
2019-02-25 18:28     ` Henning Schild

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=20190219063736.26836-2-mosipov@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