Start LAVA testing on merge requests
Value
Having simple testing on select number of targets on each merge request can be very beneficial to devs.
Description
Once we have 2 devices for each device type in the lab, we want to have simple testing in LAVA on qemu, rpi4 and nitrogen when each MR is submitted. This will not slow down the development process since those jobs will take less 5 minutes at most.
Make sure commit SHA is included in the metadata.
In scope
Run basic smoke tests on each MR. For zephyr select some basic kernel and/or semaphore/philosophers tests and run with twister in LAVA.
Out of Scope
Do not run heavy-weight tests like ltp, perf etc.
Acceptance Criteria
Applicable Market Segments
Applicable Personas
Edited by Stevan Radaković