[Fuego] Fuego 1.0.0 release

Bird, Timothy Tim.Bird at am.sony.com
Thu Nov 10 01:57:35 UTC 2016

> -----Original Message-----
> From: Daniel Sangorrin on Wednesday, November 09, 2016 4:55 PM
> > -----Original Message-----
> > From: Bird, Timothy on Wednesday, November 09, 2016 12:44 PM
> > Let me know if you see any problems.  I've foregone going through an RC
> release
> > series for this release, but I may add that if it looks like I need help from
> outside
> > parties stabilizing releases in the future.
> Thanks for the release. I reinstall everything from scratch and let you know if
> I find some problem.

Thanks.  I would especially like to know if the support for building a container
behind a proxy works right.   I wasn't able to test that.
> > Finally - I know there are pending patches on the mailing list (thanks
> Daniel).
> > I wanted to get this release out before going through those, as this release
> was
> > already complicated enough.  Just by way of information, my upcoming to-
> do list is:
> >  * figure out why there are two tests.info files, and hopefully get rid of one
> >  * evaluate Daniel's latest set of patches (from the last 2 weeks), and
> provide
> >     feedback and/or integrate them into 'next'.
> >  * start work on standards for test pre check functionality (compare with
> 0day
> >    and any other systems that do test pre check
> >  * write a target scan and health_check test
> >  * write the contract for the serial console transport feature
> Thanks, I was thinking about preparing a patch to replace tarballs by git
> repositories (using the https protocol so they can be fetched behind
> proxies).
> What do you think about that? If you think there are more urgent changes
> to make let me know.

I think this would be a nice addition.  Please don't replace tarballs, but just
add the ability to process a git URL, in addition to the current support for
de-tarring (and applying patches).  This feature would make Fuego similar
to other build systems that can retrieve source via repositories, so we might
want to use the same terminology or conventions that other systems do
(maybe copy (at least partially) what Yocto Project does, as some segment
of our user base may have experience with that).

One thing those systems support is specifying a git commit id to checkout,
along with the repository URL.

> > I know that Toshiba is working on (or plans to work on) supporting another
> > Jenkins version besides 1.509.2.  I plan to help with that if needed.  If we
> > can get Fuego to be independent of Jenkins version, that would be good.
> > That's hard at the moment, but we should see how much dependencies
> > can be reduced.
> Yes, we are looking into it. But it may take some time.

That's fine - thanks for any work you do here.

> > With regard to forks, I need to review where Cogent Embedded is with
> their stuff.
> > I noticed that the AGL-JTA CIAT project has made a few changes, but I
> believe
> > the script engine (which has changed in Fuego but not in AGL-JTA, I
> believe)
> > is still compatible with their tests.  This is also something that needs review.
> I believe they want to reduce the gap and contribute back some of the
> changes
> they made. However, I think that some changes (e.g.: use of LAVA) will not
> fit
> with our idea of having a simple and compact testing tool that is easy to
> install, use
> and visualize results with.

So far, I think we've maintained compatibility at the script level.  So, cogentembedded
and AGL-JTA are still using, to my knowledge, the Fuego test API.  I think this is the most
important thing going forward, and I want to make sure we don't break that.  So, I'm trying
hard to only add features, and to support backwards compatibility when I do.

 -- Tim

More information about the Fuego mailing list