[Fuego] Fuego 1.0.0 release

Daniel Sangorrin daniel.sangorrin at toshiba.co.jp
Mon Nov 14 04:19:59 UTC 2016

> -----Original Message-----
> From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-bounces at lists.linuxfoundation.org] On Behalf Of Daniel Sangorrin
> My opinion is that if we are not going to use Jenkins functionality and plugins
> we might as well drop it. For example, we could just focus on the command
> line version (ftc) and then develop a reference front-end on a separate repository.
> That front-end could be just Jenkins. But honestly, I don't think that Jenkins
> excels as a front end. The interface is hard to modify (oh Java!)  and not as flexible
> as one could wish. Plus I don't like the idea of using plugins because they come and
> go as they change the interface with new versions.

Maybe I said to much here.
For now Jenkins is probably the best solution as reference front-end 
because developing a new front-end will require too much resources.

> This has another side advantage: we can download the tests' source code in a "lazy" fashion
> (i.e.: when the test is run for the first time) instead of having to download everything
> when installing Fuego from scratch.

By "This" I mean decoupling the source code from the Fuego repository.


IoT Technology center
Toshiba Corp. Industrial ICT solutions, 

More information about the Fuego mailing list