All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Random build results now available online
Date: Wed, 21 Mar 2012 10:13:27 +0100	[thread overview]
Message-ID: <20120321101327.49d34f93@skate> (raw)

Hello,

During the Prague and Brussels last Buildroot meetings, we discussed
the idea of putting online the results of the random configurations
build that Peter and myself were doing.

This week-end, I want ahead and implemented something. The results of
both Peter builds and my builds are now visible online at:

 http://buildroot.humanoidz.org/

Builds are running 24/7 on several machines (one build server of Free
Electrons, and multiple machines of the gcc farm), and all results are
visible online. For each result, one can see:

 * the result (OK or NOK)
 * the Git commit id identifying which Buildroot version was used. The
   build machines are updating their version before every build
 * which architecture was targeted
 * which package is failing
 * which machine was used for the build
 * the 100 last lines of the build log (faster than having to download
   the entire build log)
 * the entire build log compressed
 * the Buildroot configuration

In the following days, I will:

 * Put online the source code of the web interface. It consists of a
   bit of crappy PHP code, but I'll put it online in a Git repository
   so that everyone can contribute to its improvement.

 * Put online a documentation that details how other people can
   contribute build results (it's basically a matter of creating a
   tarball with some particular files, and uploading this tarball over
   http)

The website along with all build results are currently hosted on a
personal server. If there a wish to migrate this on a more common
server, I'll be happy to do so, provided that this server has the
necessary ressources (dependencies and disk space).

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2012-03-21  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  9:13 Thomas Petazzoni [this message]
2012-03-21  9:27 ` [Buildroot] Random build results now available online Peter Korsgaard
2012-03-21  9:42   ` Thomas Petazzoni
2012-03-21  9:50     ` Peter Korsgaard
2012-03-21 11:42 ` Luca Ceresoli
2012-03-21 12:20   ` Thomas Petazzoni
2012-03-21 12:54     ` Peter Korsgaard
2012-03-21 13:00       ` Thomas Petazzoni
2012-03-21 11:48 ` Nikolay Nikolaev
2012-03-21 12:15   ` Thomas Petazzoni
2012-03-21 13:00   ` Thomas Petazzoni
2012-03-21 13:10     ` Nikolay Nikolaev
2012-03-21 13:17       ` 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=20120321101327.49d34f93@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 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.