On Tue, 28 Apr 2015 12:42:11 +0200 Marco Felsch marco.felsch@gmail.com wrote:

Dear Linaro Developer,

First of all you made a very great validation system *thumbs up*

I had set up a LAVA instance 2 weeks ago and all works well. But there are a few questions.

1. I use the “deploy_kernel” options, but with my own kernel,dtb and

rootfs (and my own prompt).It is possible to define the “prompt” in the “deploy_kernel”-section?

https://validation.linaro.org/static/docs/qemu-deploy.html?highlight=test_im...

It's part of the boot parameters.

2. I had read a lot of stuff on the LAVA doc-site and on many

presentations and I saw your Jenkins-LAVA setup. How do I configure the LAVA Server, that he triggers test-jobs after a successful Jenkins-build?

I think that's the wrong way around. Jenkins is doing the build, so Jenkins knows when the build is successful (as far as compilation and any build tests), so Jenkins should submit the job to LAVA to do a test using the result of the build.

For this to work, Jenkins needs to:

0: have somewhere to put the files you need from the build 1: Populate a JSON job template with data from this build and those file locations. a: always do that in a language which understands JSON, modify in memory and dump the completed JSON back ou. 2: use the XMLRPC support to submit-job a: that will need a token to be created by the jenkins user in LAVA (or ci-admin or whatever you call the user submitting these Jenkins jobs).