Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] autobuild annotations
Date: Wed, 20 Nov 2013 12:03:30 +0100 (CET)	[thread overview]
Message-ID: <403618053.13241218.1384945410540.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20131120115934.356d52c3@skate>





> 
> Jenkins just doesn't work for random builds.
> 
> Jenkins is designed to build the same configuration over and over
> again, and make comparisons from one build to another: the build was
> working yesterday, it's failing today, here is the set of commits
> that
> have been made between yesterday and today, and therefore the problem
> is somewhere in these commits. Jenkins is really good for that, and
> we
> already use it to build all the Buildroot defconfigs every day.
> 
> 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...

  reply	other threads:[~2013-11-20 11:03 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 [this message]
2013-11-20 11:11       ` Thomas Petazzoni

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=403618053.13241218.1384945410540.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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