On 07/23/2012 11:11 AM, Marek Vasut wrote:
Dear Tom Rini,
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.
But then, do we really need to poke into this now? Maybe we should look more into the PW first
Me or the community? I'm going to poke Jenkins regardless since it's something I've got setup already (and I've contributed a few changes and a plugin, in a past life). Is it the right answer for the community? TBD :) Is it the first thing we should address? No, the patch collection / management problem should indeed come first.