Bug 6425

Summary: Add ability to build a task in isolation
Product: [Build System, Metadata & Runtime] BitBake Reporter: Paul Eggleton <bluelightning>
Component: bitbakeAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: Low CC: poky.bs.watcher, poky.watcher, richard.purdie
Version: 1.7   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Paul Eggleton 2014-06-11 13:25:50 UTC 
Sometimes you just want to build an individual recipe or task whilst still taking care of dependencies, but not being concerned if one has changed signature. For example, if you force rebuild the kernel currently anything that depends on the kernel rebuilds as well, which is usually unnecessary if you're just working on a part of the kernel and not changing any of the ABI that those other recipes care about (which would probably be most of the time).

We could look at adding the ability to build an individual task/tasks in isolation without worrying about whether other tasks have changed hashes ("uncached mode" as Richard describes it ?) as a way to solve this.
Comment 1 Stephen K Jolley 2017-09-14 15:05:25 UTC 
Still a good idea.
Comment 2 Richard Purdie 2018-04-18 16:01:33 UTC 
You can do this today with bitbake -b. 

Another option is locked signatures which also gives a mechanism to do this although without a good UI. A rough possible UI type workflow could be:

bitbake-lock lock *
bitbake-lock unlock bash
bitbake bash

or similar. The backend mechanism exists but the UI tooling does not.
Comment 3 Paul Eggleton 2019-07-04 10:02:54 UTC 
Marking this one as a duplicate of bug 13425 since we've solidified our idea around how this should work there.

*** This bug has been marked as a duplicate of bug 13425 ***