public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/2] cachability: ignore BBLAYERS in get_build_id
Date: Wed, 31 Aug 2022 15:30:56 +0200	[thread overview]
Message-ID: <20220831133057.216312-1-felix.moessbauer@siemens.com> (raw)

The get_build_id task just provides a convenience check for
issues around a missed ISAR_RELEASE_CMD.
While it uses the BBLAYERS variable internally, this does not
have any effect on a generated artifact, hence the value of the
variable can be ignored.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes/image.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ba2dfa87..ccff8106 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -308,6 +308,7 @@ python() {
 # this could be "git describe" or something similar.
 # set ISAR_RELEASE_CMD to customize, or override do_mark_rootfs to do something
 # completely different
+get_build_id[vardepsexclude] += "BBLAYERS"
 get_build_id() {
 	if [ $(echo ${BBLAYERS} | wc -w) -ne 2 ] &&
 	   [ "${ISAR_RELEASE_CMD}" = "${ISAR_RELEASE_CMD_DEFAULT}" ]; then
-- 
2.30.2


             reply	other threads:[~2022-08-31 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 13:30 Felix Moessbauer [this message]
2022-08-31 13:30 ` [PATCH 2/2] ignore wic tasks in isar-sstate lint Felix Moessbauer
2022-09-08 14:07 ` [PATCH 1/2] cachability: ignore BBLAYERS in get_build_id Anton Mikanovich

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=20220831133057.216312-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@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