[U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12

[Tom Rini]

On Sat, Jul 21, 2012 at 03:27:30AM +0200, Marek Vasut wrote:
> Dear Tom Rini,
> 
> > On Wed, Jul 18, 2012 at 09:21:40AM +0200, Wolfgang Denk wrote:
> > 
> > [snip]
> > 
> > > And Jenkins... well, we have been using this for some time internally
> > > to run test builds for U-Boot.  I can tell you a thing or two about
> > > it, and Marek has his own story to tell about his experiences when he
> > > added to the build matrix.
> > > 
> > > As is, we try hard to get rid of Jenkins, because it does not scale
> > > well to the type of builds we want to be able to do.  Marek even
> > > started setting up his own test build framework...
> > 
> > I told Marek on IRC that I don't understand this, given a lot of the
> > things I've made Jenkins do before and that at the end of the day it's
> > $whatever-pass/fail-logic
> 
> Not really, what about the warning-logic ? Aka. I actually need jenkins to do 
> tristate results. How, I didn't figure out.

Yes, you can have the build go "yellow" for warnings.

> > on top of a bash script to do the building and
> > testing.
> 
> So in the end, jenkins is just an executor, bringing in pile of java overhead 
> and possible random breakage. I use MAKEALL in my script, which does exactly 
> what I need ... and even tests MAKEALL ;-)

Yes, you're writing your own overhead and dealing with bugs in that
rather than using an existing project :)

-- 
Tom