From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Buildhistory web interface
Date: Wed, 10 Oct 2012 00:32:22 +0100 [thread overview]
Message-ID: <2768622.DEanCvs65g@helios> (raw)
Hi all,
As part of working on buildhistory[1] I developed a Django-based web
application for reviewing warnings generated by analysing the output, and
finally it has reached a state where I can release it. It's fairly basic but
provides the following features:
* Generate warnings and import them into a database for the web UI
* List queued and reviewed warnings
* Show details on a warning
* Review a warning as "Action required", "Resolved" or "Ignored"
* Comment on a warning
* User authentiation and registration
Since it's really separate from the metadata it has been published in a
separate repository:
http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/
There's a screenshot here:
http://wiki.yoctoproject.org/wiki/File:Buildhistory-web1.png
Some further details on how to set it up and use it can be found in the README
within the repository:
http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/plain/README
There's probably some room for improvement especially with how the warnings
are presented, and the code to generate the warnings (which is within the
metadata and is shared with the existing buildhistory-diff command line
utility) may benefit from some further work also. I'm by no means a web
development expert either so if you have any suggestions or patches in that
regard I'd be happy for those as well.
Cheers,
Paul
[1] http://wiki.yoctoproject.org/wiki/Buildhistory
--
Paul Eggleton
Intel Open Source Technology Centre
reply other threads:[~2012-10-09 23:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2768622.DEanCvs65g@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox