Bitbake does not record locations where the variables are changed.

Fixing this would require an important change in Bitbake, which could severely impact the performance; setVar needs to record the backtrace of where it is called and save it in a var flag.

Propose delay for 1.5.X

moved to 1.5.1

I would propose modifying bitbake to keep track in a variable flag the current file:line of code where a variable is modified. 

Opinions ?

When history tracking is turned on it definitely does record this information. You can see it in the bitbake -e output.

I got this info on bitbake -e. 

#
# $B_pn-xcb-util-image
#   [no history recorded]
#
#   "${SEPB}"
B_pn-xcb-util-image="/home/ddalex/ssd/yocto/build/tmp/work/x86_64-poky-linux/bblayers/1.0-r0/build"
#
# $localstatedir
#   [no history recorded]
#
#   "${base_prefix}/var"
export localstatedir="/var"


Am I doing something wrong ?

Something is going wrong there because my equivalent here is:

#
# $B_pn-xcb-util-image
#   set /home/paul/poky/poky/meta/conf/distro/include/seperatebuilddir.inc:706
#     "${SEPB}"
B_pn-xcb-util-image="/home/paul/poky/poky/build/tmp/work/i586-poky-linux/bblayers/1.0-r0/build"
#
# $localstatedir [2 operations]
#   exported conf/bitbake.conf:31
#     [export] "1"
#   set conf/bitbake.conf:31
#     "${base_prefix}/var"
# computed:
#   "${base_prefix}/var"
export localstatedir="/var"

Fix merged in origin/master and origin/dora-toaster. 

The file field is deleted.

There is a new table, orm_variablehistory, that tracks all changes for a variable. The REST API page have been modified to document the API change, but the patchset for the API change was not merged yet.

Verified in

master:b0281b3a190dec6502b4abc6a5b14ae46243f913 

dora-toaster:1182665de0da9a6e5fc77107f32a7fc1515029d0