Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Webtool to analyze package build fail/pass from autobuild
Date: Wed, 19 Oct 2016 15:10:11 +0200	[thread overview]
Message-ID: <20161019151011.68cc5079@free-electrons.com> (raw)
In-Reply-To: <1476882214.26312.22.camel@synopsys.com>

Hello,

On Wed, 19 Oct 2016 13:04:04 +0000, Alexey Brodkin wrote:

> > As this tools have been proven to be of great value to us, perhaps you
> > would feel the same.
> > The code is shared in:
> > https://github.com/foss-for-synopsys-dwc-arc-processors/buildroot_stats
> > 
> > Looking forward for your feedback.?  
> 
> I'm wondering if there's any interest in proposed thing from your side?

Yes, sorry for not replying earlier. Recent times have been busy with
ELCE and the Buildroot meeting. It definitely looks interesting, but I
want to take a closer look before giving some detailed feedback.

> We may indeed deploy it on some public server and encourage people
> to start using that but I'm not sure if there's a point in adding
> "3rd-party" services around?http://autobuild.buildroot.net/?instead
> of enhancing autobuild server itself.

Fully agreed.

Though one initial issue is that Cupertino wrote his logic in Ruby
(which I don't really read/write). The existing autobuild.buildroot.net
code base is some horrible PHP crap that I wrote. I'm hoping to rewrite
that crap someday, but definitely not in Ruby, but rather in Python,
which is more widely used in the Buildroot community than Ruby, and
also a language that I happen to read/write (even though my Python-fu
is really basic, it's good enough for this kind of stuff).

But I guess this is just an implementation detail, and we can work in
bringing Cupertino's logic in autobuild.buildroot.net somehow.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-10-19 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 11:44 [Buildroot] Webtool to analyze package build fail/pass from autobuild Cupertino Miranda
2016-10-19 13:04 ` Alexey Brodkin
2016-10-19 13:10   ` Thomas Petazzoni [this message]
2016-11-01 15:56     ` Cupertino Miranda

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=20161019151011.68cc5079@free-electrons.com \
    --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