From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] autobuild annotations
Date: Wed, 20 Nov 2013 12:11:48 +0100 [thread overview]
Message-ID: <20131120121148.79482e2b@skate> (raw)
In-Reply-To: <403618053.13241218.1384945410540.JavaMail.root@openwide.fr>
Dear Jeremy Rosen,
On Wed, 20 Nov 2013 12:03:30 +0100 (CET), Jeremy Rosen wrote:
> > However, what autobuild.buildroot.org is doing are *random*
> > configurations. I.e you cannot compare one build to another. This
> > really doesn't fit well in the model of Jenkins in my opinion, and
> > is the reason why a small specific tool was written.
>
> couldn't failed build configurations be forwarded to jenkins for
> monitoring ?
>
> Jenkins could drop those compilations once they work again, that
> would provide some form of followup...
Is this really needed? I mean, the autobuilders are already showing us
when a problem occurs, and then we fairly quickly see when it no longer
occurs.
Of course, if someone wants to set up a Jenkins that does this, I have
no problem changing the autobuild.buildroot.org thing to forward broken
configurations to some Jenkins instance. But I personally don't think
it's really worth the effort.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-20 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 9:57 [Buildroot] autobuild annotations Thomas De Schampheleire
2013-11-20 10:38 ` arnaud aujon
2013-11-20 10:59 ` Thomas Petazzoni
2013-11-20 11:03 ` Jeremy Rosen
2013-11-20 11:11 ` Thomas Petazzoni [this message]
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=20131120121148.79482e2b@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox