On 21 March 2016 at 15:16, Marc Titinger mtitinger@baylibre.com wrote:
I get your point, but I'm not 100% clear why we still need two different actions/classes, since both lava-command and lava-test-shell will only allow running commands on the target (or a node more generally), unless adding host-side hooks. Does this limitation remain with the pipeline mode ?
There are a number of inconsistencies and workarounds in V1, hence the work on V2.
There is no equivalent of lava_command in V2. Job metadata in V2 will be job-specific, retaining metadata within test shell definitions, specific to that test shell definition, including inline definitions. I'm not really sure what you're trying to achieve with lava_command, but if you are running commands on the device, a test definition is the way to do that and to have definition-specific metadata.