Bug 12749 - Add ability to do "preflight" by using sstate
Summary: Add ability to do "preflight" by using sstate
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 2.6 M3
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-05-15 08:46 UTC by Bill Mills
Modified: 2018-08-14 10:46 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Mills 2018-05-15 08:46:31 UTC 
Bitbake should have the ability to let the user know how many tasks need to be redone vs reused from sstate.

I envision that the user is expecting a trivial rebuild but by accident changes something that will force a rebuild of many things.  The user should be able to cancel the build before much happens.

I expect the user would opt-in to a "continue Y/n" prompt.  If the check itself is quick it could be included by default as a message.
Comment 1 Richard Purdie 2018-08-07 16:38:21 UTC 
There are patches on the bitbake-devel and openembedded-core mailing lists which when combined add an sstate usage summary to the build output.

This output is printed early in the build so you can quickly break out if its not what you expect. Its also printed if you run bitbake with the --dry-run option.