[OE-core] Running BitBake multiple times without rechecking upstream AUTOREV versions
Richard Purdie
richard.purdie at linuxfoundation.org
Mon May 14 08:20:06 UTC 2018
On Fri, 2018-05-11 at 18:23 +0000, Chris Laplante via Openembedded-core
wrote:
> Hi all,
>
> I’m working on using Jenkins to host our Yocto build. One of the
> things that would be nice is to be able to do a “bitbake our-user-
> image”, upload the artifacts to our network file storage, and then do
> a “bitbake our-user-image -c populate_sdk_ext”. I’d like to do these
> separately so that developers are not waiting around for the eSDK to
> be generated if all they care about is the kernel, for example. My
> concern is that the second bitbake invocation could end up building
> different stuff if someone were to check in code in between when the
> two “bitbake”s are run. This is primarily a concern with recipes that
> use AUTOREV (as we do for development purposes).
>
> Is there a way to essentially “freeze” the BitBake data store and re-
> use it across multiple bitbake invocations?
Have you tried BB_SRCREV_POLICY = "cache"?
Cheers,
Richard
More information about the Openembedded-core
mailing list