Neil Williams neil.williams@linaro.org writes:
The 2016.2 release is the point at which pipeline moved out of developer only and became available using the production systems for the Linaro Cambridge lab. There have been a few issues with the configuration files and some parts of the CLI in 2016.2 which will be solved in the next release.
So 2016.2 can run U-Boot pipeline jobs and is doing so on staging, validation.linaro.org and lava.debian.net. Devices need to be enabled as pipeline devices in the django admin interface and the old dispatcher configuration files need to be ported to device dictionaries which are then imported into the database. We're also updating the documentation on how to do that after feedback from those who have already used the pipeline dispatcher. https://review.linaro.org/#/c/10428/
We are aiming to get all the issues with 2016.2 fixed for 2016.3, hopefully before Connect BKK16 in March but it might need to wait until just after we return.
Note: There is an upcoming change to the syntax of the YAML files used for U-Boot to make the compression handling more straightforward. So be ready for some changes in the deploy: blocks:
kernel: http:// ramdisk: http://
becomes
kernel: url: http:// ramdisk: url: http:// compression: gz
We'll be updating the documentation at the same time: https://review.linaro.org/#/c/10589/1/doc/dispatcher-actions2.rst as well as updating the pipeline jobs at https://git.linaro.org/lava-team/refactoring.git
It sounds to me like things are still in a fair amount of flux, so switching now might require a fair amount of babysitting (e.g on-going changes in YAML syntax are not something I feel like wanting to keep track of.)
Is there a freeze point coming where it might make more sense to switch over?
Kevin