From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 23 Jul 2012 10:28:49 -0700 Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 In-Reply-To: <201207231917.15247.marex@denx.de> References: <201207210327.30973.marex@denx.de> <20120723164419.GB22955@bill-the-cat> <201207231917.15247.marex@denx.de> Message-ID: <500D89D1.40602@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 07/23/2012 10:17 AM, Marek Vasut wrote: > Dear 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. > > How? Post build stuff and promoted builds. I'm hopeful once I get a few patch series polished up and posted for v2012.11 I can go back and give my Jenkins instance some more attention. >>>> 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 :) > > Well, jenkins just crashed so badly I didn't manage to get it back in a working > state, you know ... Never had that happen, sorry :) -- Tom