Bug 1890 - Build history analysis web interface
Summary: Build history analysis web interface
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium enhancement
Target Milestone: 1.3 M4
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-01-11 02:33 UTC by Paul Eggleton
Modified: 2013-01-03 15:58 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2012-01-11 02:33:42 UTC
Create a web interface to display and manage the output of the analysis tool created for bug #1566. We already have the logic implemented in a reusable manner (meta/lib/oe/buildhistory_analysis.py), so this can be used to generate the items and then allow the user to review each one and mark it as OK or needing further action.
Comment 1 Paul Eggleton 2012-10-08 23:32:10 UTC
The code has now been released:

http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/

See the README in the repository for further details.
Comment 2 Stoicescu Cornel 2012-11-07 13:57:41 UTC
Hello

I have installed django and all needed for it to work. I am following your README file but when running the server using "python manage.py runserver" I get the following error(on the server-side) when accessing the site: 
Validating models...

0 errors found
Django version 1.4.2, using settings 'buildhistory.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
Traceback (most recent call last):
  File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
    self.result = application(self.environ, self.start_response)
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line 241, in __call__
    response = self.get_response(request)
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 179, in get_response
    response = self.handle_uncaught_exception(request, resolver, sys.exc_info())
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 224, in handle_uncaught_exception
    if resolver.urlconf_module is None:
  File "/usr/local/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 323, in urlconf_module
    self._urlconf_module = import_module(self.urlconf_name)
  File "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 35, in import_module
    __import__(name)
ImportError: No module named warningmanager.urls

I have django 1.4 installed and the first part of the django tutorial works fine on my machine: https://docs.djangoproject.com/en/1.4/intro/tutorial01/

I am using Ubuntu 12.04.
Comment 3 Paul Eggleton 2012-11-13 14:45:50 UTC
I've entered bug 3412 to cover this; seems there are some deployment issues.
Comment 4 Stoicescu Cornel 2012-11-13 16:47:08 UTC
Due to deployment issues, I was unable to verify this. Setting it to reopened.
Comment 5 Paul Eggleton 2012-12-06 11:45:26 UTC
I've pushed several fixes that should help deployment to the buildhistory-web master branch - Corneliu could you please retest?
Comment 6 Paul Eggleton 2012-12-12 23:00:28 UTC
I'm marking this as resolved again as I believe it is now fixed.
Comment 7 Stoicescu Cornel 2012-12-13 08:59:44 UTC
I will test this next week and pass here the result.
Comment 8 Stoicescu Cornel 2013-01-03 15:58:11 UTC
Verified in buildhistory-web: 473c6c505ea7ed0475dd686e8662753b2f831abf. Flowing the instructions in the README file, the web application works with no issues.