I found a failing one, I need to find wht jenkins give the wrong vcs_branch master instead of guppy

http://lava.automotivelinux.org/scheduler/job/3496

I have triggered a build:

[https://build.automotivelinux.org/job/ci-apps-hvac-verify-master-CIBT-x86-64/4/console]

which resulted in a successful testjob:

https://lava.automotivelinux.org/scheduler/job/3427

I created 2 sample jobs that we can work on:

a) master + wgt file   (= take filesystem from snapshot)

https://lava.automotivelinux.org/scheduler/job/3341

with the description:

note: rootfs/kernel come from snapshots while the APPURL is the GERRIT_CHANGE_NR/GERRIT_PATCHSET_NR .

b) guppy + wgt file  (= take filesystem from releases)

https://lava.automotivelinux.org/scheduler/job/3343

 Note: rootfs from release dir (latest) and wgt from CI upload folder.

Yes, we have 2 pieces here:

a) the qemu system binaries need to be taken from a certain directory "A" , for example the snapshot directory  https://download.automotivelinux.org/AGL/snapshots/master/latest/qemux86-64/deploy/images/qemux86-64/  in this case (usually) - but we also might imagine to take a release, btw.

b) the application artifact/wgt file that was just built and is referenced by the ChangeNR/PatchsetNR .

There are several problems with the app lifecycle testing

1) releng-scripts is generating platform-tests (smoke, busybox, service-check, ptests, etc.) as well as the application-lifecyle test. It should only to the app lifecycle test. You need to pass the --test option to create-jobs.py so that it only picks one of the test-plan templates. (.e.g. --test application-lifecycle)

2) When the application-lifecycle test runs, the APPURL argument is incorrect, so the test fails. Here's an example:

Taken from: https://build.automotivelinux.org/job/ci-apps-agl-service-platform-info-verify-master-CIBT-x86-64/23/consoleFull