From: Anton Mikanovich <amikan@ilbers.de>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"ubely@ilbers.de" <ubely@ilbers.de>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: ISAR schroot mountpoints when running in container
Date: Fri, 1 Jul 2022 15:08:37 +0300 [thread overview]
Message-ID: <198f52fb-c71e-7dea-8736-7443487a6bd8@ilbers.de> (raw)
In-Reply-To: <AM9PR10MB48693A1C09FF9F933032B97289BD9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
01.07.2022 14:30, Moessbauer, Felix wrote:
> Required changes:
>
> In ISAR, we have to make the name of the Schroot folder more unique. But as BB requires recipes to be deterministic (per-build), we have to inject the ID from the outside. This could happen either via local.conf or via an env-var. This env-var has to be provided by KAS, with an fallback in ISAR to use the PID of the bitbake process if not provided.
>
> A probably better strategy would be to get a per-bitbake invocation constant UUID directly from Bitbake. Don't know if that already exists in BB.
> Putting Adriaan in CC.
>
> Felix
Hello, I've already proposed unique per-build ID generation in '[PATCH
2/6] base: Implement bitbake build ID'.
Not sure it suits mentioned requirements, but can be good starting point.
next prev parent reply other threads:[~2022-07-01 12:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 9:11 Moessbauer, Felix
2022-07-01 9:27 ` Bezdeka, Florian
2022-07-01 9:36 ` Moessbauer, Felix
2022-07-01 10:05 ` Bezdeka, Florian
2022-07-01 10:23 ` Uladzimir Bely
2022-07-01 10:30 ` Bezdeka, Florian
2022-07-01 10:43 ` Jan Kiszka
2022-07-01 11:30 ` Moessbauer, Felix
2022-07-01 11:38 ` Henning Schild
2022-07-01 11:48 ` Bezdeka, Florian
2022-07-01 12:08 ` Anton Mikanovich [this message]
2022-07-01 12:25 ` Moessbauer, Felix
2022-07-01 15:07 ` Gylstorff Quirin
2022-07-05 13:40 ` Moessbauer, Felix
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=198f52fb-c71e-7dea-8736-7443487a6bd8@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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