FIXME! Needs much more text
#
.Warning
The migration to a pipeline job is not a simple case of reformatting JSON. There is no direct equivalence between the old JSON and the pipeline YAML. It is imperative that the test writer fully understands the reasons why the old JSON job does the things it does before starting to migrate that job to the pipeline.
The pipeline support is changing the way that the test jobs run so that some device types change and some multinode jobs can become single node. e.g. the old KVM device type is now QEMU, with the architecture of the QEMU binary specified by the test job. Equally, the availability of LXC and other protocols means that there is often no need for a KVM to run ADB or other components.
XML-RPC: scheduler.get_pipeline_device_config
Device type detail: Deployment, boot and protocol tabs.
The range of deployments available in the pipeline dispatcher are being enlarged, according to what Test Plans are required. Talk to the Automation & CI team at Linaro about how to coordinate the needs of your team with the available support and the planned developments.
The deployments for a pipeline job determine how the test files and the LAVA test shell overlay files are delivered to the device prior to boot. This can include making the files available for TFTP or copying the files over to a running device using SCP.
The deployment method chosen must match the boot method requirements and it is up to the test writer to ensure that a valid combination of deployment and boot methods are used.
The boot method dictates how the device is instructed to boot. Depending on the method, this will usually also involve how to deliver the deployed files to the device, e.g. using TFTP, as well as controlling the commands sent to the device to set boot options and commands.
The MultiNode Protocol is common to all device types. Other protocols may require specific configuration for the device type or not be available for all devices or on all instances.