This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
agl-testframework:setup [2016/07/13 21:00] jsmoeller |
agl-testframework:setup [2016/10/12 13:49] jsmoeller |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | ===== Workflow ===== | ||
- | |||
- | The setup supports multiple operation methods: | ||
- | * Code-change trigger: | ||
- | * Gerrit triggers JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
- | * Scripted trigger: | ||
- | * Script triggers JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
- | * Manual trigger: | ||
- | * Manual trigger in JTA, which runs the test. Board allocation and bring-up is handled by Lava. | ||
- | * Direct test: | ||
- | * Board allocation, bring-up and test execution through Lava. | ||
===== Setup ===== | ===== Setup ===== | ||
Line 19: | Line 7: | ||
* Caveats: | * Caveats: | ||
- | * AGL-JTA/Fuego assumes access through ssh to the board, right now we use a VPN between JTA and the Lava instance. This should be replaced by a transparent remote API (to support distributed aspect). | + | * AGL-JTA/Fuego assumes access through ssh to the board, right now we use a VPN between JTA and the Lava instance. This should be replaced by a transparent remote API (to support distributed aspect). Support exists but needs to be enhanced (LAVA 'hack' session). |
+ | |||
+ | ===== Adaptions / Scripts ===== | ||
+ | * You need to setup /var/lib/jenkins/lava.yaml with the server and credentials. | ||
+ | * LAVA needs the nbd-root patches (not yet upstream, find the modifications here: not polished, yet ) | ||
+ | * Dispatcher - https://paste.debian.net/795073/ | ||
+ | * Scheduler - https://paste.debian.net/795075/ | ||
+ | * http://bit.ly/lavasetup | ||
+ |