Adding test jobs to Jenkins
To add jobs to Jenkins, you use the 'ftc' command line tool.
Fuego comes with over a hundred different tests, and not all of them will be useful for your environment or testing needs.
In order to add jobs to Jenkins, you first need to have created a Jenkins node for the board for which you wish to add the test. If you have not already added a board definition, or added your board to Jenkins, please see: Adding a board
One your board is defined as a Jenkins node, you can add test jobs for it.
There are two ways of adding test jobs, individually, and using testplans. In both cases, you use the 'ftc add-jobs' command.
Run this command inside the docker container, by going to the shell prompt inside the Fuego docker container, and typing
To see the list of plans that come pre-configured with Fuego, use the command 'ftc list-plans'.
A plan lists a set of tests to execute. You can examine the
list of tests that a testplan includes, by examining the testplan
file. The testplan files are in JSON format, and are in the
The options available are:
- rebuild flag
- reboot flag
- precleanup flag
- postcleanup flag
See 'ftc add-jobs help' for details about these options and how to specify them.
For example, the following would add a job for Functional.hello_world to each of the boards rpi1, rpi2 and beaglebone.
To create a set of jobs related to docker image testing, for the 'docker' board on the system, do the following:
To create a set of jobs for a board called 'beaglebone', do the following:
The "smoketest" testplan has about 20 tests that exercise a variety of features on a Linux system. After running these commands, a set of jobs will appear in the Jenkins interface.
Once this is done, your Jenkins interface should look something like this: