Debugging sstate-cache


we have a build server set that is used by multiple
people all working on the same yocto project each
having a clone in their working dir.

The core packages (those coming from meta-openembedded)
are same of every image we build.

We all share a sstate-cache and a downloads cache.
The download cache works as expected, I only notice
new things being fetched when there were actual changes in
the recipes.

However, all other steps (do_configure, do_compile, do_package)
seem to be executed arbitrarily without a specific order or cause.
Lot of things are reused from the sstate-cache, some get redone
on random, and a few are always build from the ground.

I have synced with everyone and confirmed that we're not stepping
on each others toes by cleaning package caches.

Is there a way to see on what grounds does bitbake chooses
to repeat the steps?

Be Well,

Join to automatically receive all group messages.