Hi Alex,
On 25.10.24 11:07, Alexander Kanavin wrote:
On Thu, 24 Oct 2024 at 19:26, Philip Lorenz via lists.yoctoproject.org
<philip.lorenz=bmw...@lists.yoctoproject.org> wrote:
Is this issue generally known and are there any other recommendations on
how to deal with this?
I don't really know much about this, but I would consider allocating
PR values only for things that have been reviewed merged and landed in
trunk via separate after-the-fact release pipeline. Volatile CI stuff
should perhaps be run without enabling the PR server at all.
Wouldn't we then see version-going-backwards errors in the validation
builds (as the "mainline" builds which contribute to the shared
buildhistory will have higher PRs from PRserv)? We'd like to maximize
our cache reuse so in a perfect world even the write_package_* tasks
could be reused between the builds (which I believe we could do if we
combine hash equivalence with a non-cached packagedata task).
Philip
--
Philip Lorenz
BMW Car IT GmbH, Software-Plattform, -Integration Connected Company,
Lise-Meitner-Straße 14, 89081 Ulm
-------------------------------------------------------------------------
BMW Car IT GmbH
Management: Chris Brandt and Michael Böttrich
Domicile and Court of Registry: München HRB 134810
-------------------------------------------------------------------------
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64127): https://lists.yoctoproject.org/g/yocto/message/64127
Mute This Topic: https://lists.yoctoproject.org/mt/109194097/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
