public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH v2] scripts/ci: rebuild recipes based on dpkg-base
Date: Fri, 23 Nov 2018 10:52:26 +0100	[thread overview]
Message-ID: <20181123095226.3316-1-henning.schild@siemens.com> (raw)
In-Reply-To: <50a79648-005a-6504-5534-c69fa3e35a84@ilbers.de>

This commit adds rebuilding to CI and shows the current rebuilding
issues in Isar. After they are fixed it will be a general improvement to
CI to make sure we do not run into similar problems again.

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 d5e4d41..54adc9d 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -108,3 +108,8 @@ else
     # qemu-user-static of <= buster too old to build that
     #multiconfig:qemuarm64-buster:isar-image-base
 fi
+
+# trigger a rebuild of an image, this should be the last step since we
+# make the tree dirty and do not clean up
+echo -e "do_fetch_append() {\n\n}" >> ${ISARROOT}/meta/classes/dpkg-base.bbclass
+bitbake $BB_ARGS multiconfig:qemuamd64-stretch:isar-image-base
-- 
2.19.1


  reply	other threads:[~2018-11-23  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  9:12 [PATCH] " Henning Schild
2018-11-22  9:15 ` Henning Schild
2018-11-22  9:15 ` Jan Kiszka
2018-11-22  9:40   ` Henning Schild
2018-11-23  7:05 ` Maxim Yu. Osipov
2018-11-23  9:52   ` Henning Schild [this message]
2018-11-23  7:09 [PATCH v2] " Maxim Yu. Osipov
2018-11-23  9:54 ` Henning Schild
2018-11-23 10:23 ` 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=20181123095226.3316-1-henning.schild@siemens.com \
    --to=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