All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: oestats: build statistics for OpenEmbedded
Date: Thu, 22 May 2008 10:30:40 +0200	[thread overview]
Message-ID: <48352F30.1070202@linuxdevelopment.de> (raw)
In-Reply-To: <48346060.1030101@bolloretelecom.eu>

nice job Jeremy
that looks very promising maybe with that we can secure configs and 
snapshots which do work.

Is it possible to sort the buildreports on machine`s and also add which 
host was used ( i686 or i686-64 ) ?
and which target was build ( gpe-image - task-boot ) ???

Cheers Robert

Jeremy Lainé schrieb:
> Hi all!
> 
> I happy to announce the availability of "oestats", a web application
> for collecting and viewing OpenEmbedded build reports. In keeping with
> OE / bitbake it is written in Python and uses the Django web framework.
> 
> A live demo is available at:
> 
> http://oestats.jerryweb.org/
> 
> If you want to add your build stats, make sure your copy of OE is up
> to date and add the following to your build/conf/local.conf:
> 
> |INHERITS += "oestats-client"
> OESTATS_SERVER = "oestats.jerryweb.org"
> OESTATS_BUILDER = "your_nickname"|
> 
> Fair warning: this is a test server, no promises on availability
> though I'll do my best :)
> 
> Source code and setup notes for the server are available at:
> 
> http://opensource.bolloretelecom.eu/projects/oestats/
> 
> Your feedback and improvements are most welcome!
> 
> Cheers,
> 



  reply	other threads:[~2008-05-22  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 17:48 oestats: build statistics for OpenEmbedded Jeremy Lainé
2008-05-22  8:30 ` Robert Wörle [this message]
2008-05-22 11:34   ` Philip Balister
2008-05-22 17:23   ` Jeremy Lainé

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=48352F30.1070202@linuxdevelopment.de \
    --to=robert@linuxdevelopment.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.