From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Webtool to analyze package build fail/pass from autobuild
Date: Wed, 19 Oct 2016 13:04:04 +0000 [thread overview]
Message-ID: <1476882214.26312.22.camel@synopsys.com> (raw)
In-Reply-To: <EB86EB452ADE4B44B294F7149B8A277702219383@DE02WEMBXB.internal.synopsys.com>
Hi Thomas,
On Tue, 2016-10-11 at 11:44 +0000, Cupertino Miranda wrote:
> Hello everyone,
>
> I am part of the ARC GNU team at Synopsys.
> More recently in order to analyze progress in buildroot package builds,
> I created a web tool that recovers latest build information from
> autobuild.buildroot.net and creates an internal database and web-tools
> to access it.
>
> This database/webtool is organize such that we can track progress of
> which packages are failing or passing at any specific moment, and trace
> this failures to a specific build where we can analyze any of the build
> related logs.
>
> Moreover, each day/week the tool generates a report sent to all the
> team, where it clearly specifies which packages started failing or
> passed during the period.
>
> 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?
This tool works for us internally for quite some time now,
still I think others may benefit from it too.
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.
-Alexey
next prev parent reply other threads:[~2016-10-19 13:04 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 [this message]
2016-10-19 13:10 ` Thomas Petazzoni
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=1476882214.26312.22.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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.