From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Sat, 21 Jul 2012 03:27:30 +0200 Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 In-Reply-To: <20120720225122.GA32472@bill-the-cat> References: <20120718072140.BA23B202271@gemini.denx.de> <20120720225122.GA32472@bill-the-cat> Message-ID: <201207210327.30973.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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. > 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 ;-) Best regards, Marek Vasut