From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] scripts/ci: rebuild recipes based on dpkg-base
Date: Thu, 22 Nov 2018 10:40:09 +0100 [thread overview]
Message-ID: <20181122104009.06f45f69@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <e2a75cc5-ef2d-f764-f043-22b76548d3ef@siemens.com>
Am Thu, 22 Nov 2018 10:15:51 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 22.11.18 10:12, [ext] Henning Schild wrote:
> > 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 | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> > index d2ed6fe..dc093ec 100755
> > --- a/scripts/ci_build.sh
> > +++ b/scripts/ci_build.sh
> > @@ -102,3 +102,7 @@ else
> > # qemu-user-static of <= buster too old to build that
> > #multiconfig:qemuarm64-buster:isar-image-base
> > fi
> > +
> > +echo -e "do_fetch_append() {\n\n}" >>
> > ${ISARROOT}/meta/classes/dpkg-base.bbclass
> > +
>
> Why not destroying some stamp file instead?
I would like to see the bitbake magic work here. Problem is we leave a
dirty tree behind. We can discuss the trigger ... But as long as this
is the last thing we do, making the tree dirty is ok.
Henning
> > +bitbake $BB_ARGS multiconfig:qemuamd64-buster:isar-image-base
> >
>
> Otherwise, a valuable step forward.
>
> Jan
>
next prev parent reply other threads:[~2018-11-22 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 9:12 Henning Schild
2018-11-22 9:15 ` Henning Schild
2018-11-22 9:15 ` Jan Kiszka
2018-11-22 9:40 ` Henning Schild [this message]
2018-11-23 7:05 ` Maxim Yu. Osipov
2018-11-23 9:52 ` [PATCH v2] " 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=20181122104009.06f45f69@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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