I think I’m asking for precisely the opposite of this functionality?
bk build create --filter=on-target-s32k-test
but even if this was supported it wouldn’t work because my on-target tests pull artifacts built in the previous step. What I’m looking for is a way to run the previous step locally:
bk local run --filter=on-target-s32k-test
which totally works () but to then use the build artifacts from that local run in a special build in the pipeline. Something that might look like:
bk build create --filter=on-target-s32k-test --upload-artifacts="./build/*.hex"
This would create a special build (i.e. not grouped by the branch name in the list of builds like how PR builds work) that would be given the artifacts specified on the command-line where they match the
artifacts property in the step yaml.
It’d also be really cool to find out why
bk build create doesn’t work for me but I guess I should open a topic under help for that.
--filter does use the label which is weird. id would be more appropriate for this.