Here are Release Notes for the Fuego 1.1 release.

This, although specified as a "minor" release, has some major changes in Fuego.

Here are some things to look out for in converting to this release:

Major changes [edit section]

Changes to Jenkins [edit section]

Using a much more recent version of Jenkins (v2.32.1).

Using the default Jenkins interface. If you want to customize this interface you can.

Jobs for the Fuego tests are added to Jenkins using the 'ftc add-jobs' command. Jenkins nodes for Fuego boards are added to Jenkins using the 'ftc add-nodes' command.

Builds show a link to the test log (and to a plot of Benchmark data, if applicable) on the build page in the Jenkins web interface.

Changes to directory layout [edit section]

Almost all of the Fuego directories have changed locations. They used to be expressed as a set of directories under /userdata inside the docker container (but that were mapped to a directory on the host machine, outside the container), and a set of directories under /home/jenkins.

For ease of development of the Fuego system, they are now expressed in 3 sets of directories:

• /fuego-ro
• /fuego-rw
• /fuego-core

Here are some specific directories that have moved locations:

• /userdata/conf/boards is now in /fuego-ro/boards
• /userdata/toolchains is now in /fuego-ro/toolchains
• /userdata/logs is now in /fuego-rw/logs
• /home/jenkins/fuego/engine is now in /fuego-core/engine
• <fuego-core>/engine/scripts/overlays/specs - has been removed
  • spec files are now places in their corresponding test directories
• <fuego-core>/engine/jobs - has now been removed
  • Jenkins jobs files are now created using 'ftc add-jobs'

Changes to variables [edit section]

• in the Fuego board file:
  • FUEGO_HOME is now BOARD_DESTDIR
  • DISTRIB is a new variable to declare the distribution used on a board
    • this used to be in the Jenkins node file for a node

• FUEGO_SCRIPT_PATH - is removed - use FUEGO_RW/engine/scripts
• FIXTHIS - add more here...

Future releases [edit section]

Release took a long time - almost 6 month. We would like to have shorter releases for the next year (possibly 3 or 4-months apart). We have several important features to release and we'd like to get them to users as soon as possible.