Release 1.6 Notes
- suppport for default_board
- add support for short test names
- added support for "match_board" option in chart_config
This can be used to execute tests on a particular, designated board with less typing. For example:
if fuego.conf has the line:
they you can type:
Instead of the more verbose
This can be useful if you only have a single board in your lab, or you are installing and using Fuego natively (for local access).
Note that you can achieve the same by defining the FUEGO_BOARD environment variable to "local", but specifying a default_board in the config file is a bit easier. If a default board is specified using the FUEGO_BOARD environment variable, that takes precedence over the value specified in the fuego.conf file.
Note that the bash completion was updated to support short test names. You can type 'ftc run-test -b board1 -t hello<tab>', and the shell will complete the short test name for you (to 'hello_world').
By default, Fuego has Jenkins show the test results for all of the boards that a test has run on. By setting "match_board" to "true" in the chart_config.json file for a test, only the results that match the board for the job will be displayed.
For example, for the test Functional.hello_world, if you have jobs for the boards 'bbb', 'rp4', and 'ren1', then you would have the following jobs defined in Jenkins:
The test results for all of these boards would be shown on the job page for all of these jobs. However, by adding this line to the chart_config.json file for Functional.hello_world (in the section "chart_config")
then on the bbb.default.Functional.hello_world job page, only the test results for the 'bbb' board will be shown.