Hello,
We use a python script, LAVA_via_API, to trigger our test jobs. I must say that I don't know whether this script is a pure internal creation or whether it's been inspired by a Linaro script.
Its role is simple, create a lava job with quite a few parameters (job name, server, worker, kernel, rootfs, dtb, device, device_type, and so on), submit the job, get results and logs.
Whatever, before reworking completely this script, I assume that a reference one exists on one of the Linaro gits. Can you tell me where to find this?
Thanks,
Denis
On 18 July 2017 at 10:06, Denis HUMEAU denis.humeau@st.com wrote:
Hello,
We use a python script, LAVA_via_API, to trigger our test jobs.
I must say that I don’t know whether this script is a pure internal creation or whether it’s been inspired by a Linaro script.
It is likely that this is related to the various trigger scripts used with a variety of build systems. Each will be quite different, albeit with similar objectives.
Its role is simple, create a lava job with quite a few parameters (job name, server, worker, kernel, rootfs, dtb, device, device_type, and so on), submit the job, get results and logs.
One thing to seriously consider at this stage is to use templating. Jinja2 is a powerful templating language and can be used to create test job submissions to LAVA just as it creates the device configuration within LAVA V2. KernelCI is using a method like this to construct the submissions to LAVA V2.
https://github.com/kernelci/lava-ci-staging/blob/master/jenkins/lava-boot-v2...
https://github.com/kernelci/lava-ci-staging/blob/master/lava-v2-jobs-from-ap...
Whatever, before reworking completely this script, I assume that a reference one exists on one of the Linaro gits. Can you tell me where to find this?
The QA team use a jenkins trigger script to create LAVA test job submissions.:
https://git.linaro.org/ci/job/configs.git/tree/openembedded-lkft/lava-job-de...
lava-users@lists.lavasoftware.org
-
Denis HUMEAU -
Neil Williams