From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: florian.bezdeka@siemens.com, henning.schild@siemens.com
Subject: Re: [PATCH v3 1/1] add uuid to schroot folder
Date: Fri, 8 Jul 2022 15:46:50 +0300 [thread overview]
Message-ID: <d18f84eb-25fe-2424-24be-e4eaa4827335@ilbers.de> (raw)
In-Reply-To: <20220704091557.1761054-2-felix.moessbauer@siemens.com>
04.07.2022 12:15, Felix Moessbauer wrote:
> PIDs are not unique across containers.
> When running the build in a container (e.g. the kas container),
> the PID of bitbake is likely the same across multiple simultaneously
> running builds.
>
> This is especially the case for CI runners, where it is common that
> multiple jobs run in parallel.
>
> This patch adds an additional UUID component that is injected
> from the ISAR environment.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
I'm still think placing ISAR_BUILD_UUID generaion outside bitbake is not
really
good idea. This is ok for single run inside container but not so
suitable for
running several builds in one build environment (when we source
isar-init-build-env only once and then execute bitbake over and over again).
Current implementation is more env-unique but not build-unique.
next prev parent reply other threads:[~2022-07-08 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:15 [PATCH v3 0/1] " Felix Moessbauer
2022-07-04 9:15 ` [PATCH v3 1/1] " Felix Moessbauer
2022-07-08 12:46 ` Anton Mikanovich [this message]
2022-07-08 14:37 ` 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=d18f84eb-25fe-2424-24be-e4eaa4827335@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=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