From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12
Date: Tue, 24 Jul 2012 00:16:03 +0200 [thread overview]
Message-ID: <201207240016.03230.marex@denx.de> (raw)
In-Reply-To: <500DA159.2040005@ti.com>
Dear Tom Rini,
> 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.
Just what I had in mind :)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-23 22:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:30 [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 Detlev Zundel
2012-07-16 23:11 ` Graeme Russ
2012-07-17 10:37 ` Stefan Roese
2012-07-17 12:10 ` Graeme Russ
2012-07-17 12:15 ` Graeme Russ
2012-07-18 7:21 ` Wolfgang Denk
2012-07-18 23:37 ` Graeme Russ
2012-07-21 14:46 ` Marek Vasut
2012-07-23 1:33 ` Graeme Russ
2012-07-23 1:47 ` Marek Vasut
2012-07-23 2:07 ` Graeme Russ
2012-07-23 2:13 ` Marek Vasut
2012-07-23 7:43 ` Andy Pont
2012-07-23 6:27 ` Wolfgang Denk
2012-07-23 6:20 ` Wolfgang Denk
2012-07-23 21:16 ` Tom Rini
2012-07-23 22:15 ` Marek Vasut
[not found] ` <500DD2FA.4060800@boundarydevices.com>
2012-07-23 23:06 ` Marek Vasut
2012-07-23 23:37 ` Eric Nelson
2012-07-23 6:16 ` Wolfgang Denk
2012-07-25 19:47 ` Tom Rini
2012-07-27 14:17 ` Marek Vasut
2012-07-20 22:51 ` Tom Rini
2012-07-21 1:27 ` Marek Vasut
2012-07-21 4:28 ` Graeme Russ
2012-07-23 16:49 ` Tom Rini
2012-07-23 16:44 ` Tom Rini
2012-07-23 17:17 ` Marek Vasut
2012-07-23 17:28 ` Tom Rini
2012-07-23 18:11 ` Marek Vasut
2012-07-23 19:09 ` Tom Rini
2012-07-23 22:16 ` Marek Vasut [this message]
2012-07-18 7:41 ` Wolfgang Denk
2012-07-20 3:57 ` Mike Frysinger
2012-07-21 14:40 ` Marek Vasut
2012-07-23 20:53 ` Tom Rini
2012-07-23 22:14 ` Marek Vasut
2012-07-20 16:36 ` Kim Phillips
2012-07-20 21:09 ` Marek Vasut
2012-07-20 21:34 ` Graeme Russ
2012-07-20 21:40 ` Scott Wood
2012-07-20 22:04 ` Graeme Russ
2012-07-21 14:41 ` Marek Vasut
2013-02-18 6:55 ` Simon Glass
2013-02-18 9:59 ` Wolfgang Denk
2013-02-18 10:40 ` Graeme Russ
2013-02-18 12:39 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201207240016.03230.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.