Introduction
AGL uses a combination of tools for its CI tests.
AGL-JTA (a version of
Fuego is the frontend - more information can be found here:
AGL-JTA
Lava as tool to manage the boards remotely.
Both tools can actually work independently, both can execute tests. We combine them to get the best out of both worlds:
Use-cases
From the above you can deduct the following use-cases:
In-house lab - for an isolated, in-house lab, AGL-JTA/Fuego is likely your choice. With a small set of boards on the same network, you only need AGL-JTA/Fuego - no LAVA server is needed.
Board-Farm - to scale-out the testing and parallelize the execution, we need to manage multiple boards of the same type/family and multiple different boards/brands. In this case you need LAVA to mange the boards.
Remote Labs - to distribute the boards across sites and manage them, you need LAVA.
Workflow
The setup supports multiple operation methods:
Code-change trigger:
Scripted trigger:
Manual trigger:
Direct test:
Setup