Can Twister be run without a full Zephyr source tree on the execution machine?

[igok999]

Hi,

I’m working on a distributed testing pipeline where tests are built on one machine,
but executed on a separate, lightweight container that does not contain the full
Zephyr source tree.

I’d like to understand whether Twister can be run without requiring the complete
Zephyr OS environment on the execution side.

Specifically:

• Does Twister fundamentally depend on having the full Zephyr source tree available
  at execution time?
• Is there a supported or recommended way to decouple Twister execution from a full
  Zephyr checkout (for example, using only build artifacts or a reduced environment)?

Any guidance, references, or design rationale would be greatly appreciated.

Thanks!