User Tools
agl-testframework:setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
agl-testframework:setup [2016/07/13 20:59] jsmoeller |
agl-testframework:setup [2019/11/26 16:07] (current) jsmoeller |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | FIXME | ||
| - | ===== 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 ===== | ||
| - | //The instructions are WIP// | ||
| - | |||
| - | * First setup AGL-JTA (fuego) and Lava (see respective docs atm, exactsteps follow here soon) | ||
| - | * We use a custom deploy task (CIAT.lava_deploy instead of CIAT.build_deploy) to commission the board through lava. Once the board is up, we follow the predefined workflow. | ||
| - | |||
| - | * 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-testframework/setup.1468443571.txt.gz ยท Last modified: 2016/07/13 20:59 by jsmoeller
Page Tools
