Automotive Linux Wiki

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.

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).