Remote build accross arch
Summary
In order to set the cache key to a different arch so you can pull a artefact from a cache server that was built for a different arch you need to set build-arch. In order for this to be set from the cli it needs to be a variable.
Setting sandbox:build-arch
to a variable causes a Unresolved variable
error
venvbst2 will localhost ~ projects buildstream keytest willsalmon/sandboxarch ✎ $ bst -o target_arch aarch64 build basic-import.bst
[17:17:31][--:--:--][ ][ main:core activity ] START Build
[17:17:31][--:--:--][ ][ main:core activity ] START Loading elements
[17:17:31][00:00:00][ ][ main:core activity ] SUCCESS Loading elements
[17:17:31][--:--:--][ ][ main:core activity ] START Resolving elements
print /home/will/projects/buildstream/keytest/project.conf [line 23 column 2]: {'build-arch': '%{target_arch}'}
[17:17:31][00:00:00][ ][ main:core activity ] FAILURE Resolving elements
[17:17:31][00:00:00][ ][ main:core activity ] FAILURE Build
/home/will/projects/buildstream/keytest/project.conf [line 23 column 14]: Unresolved variable: target_arch
Steps to reproduce
Set build-arch in sandbox to a variable:
sandbox:
build-arch: '%{target_arch}'
What is the current bug behavior?
Bst crashes
What is the expected correct behavior?
The sand box build-target should be set to the variable.