Merge lp://staging/~doanac/qa-dashboard/live-status into lp://staging/qa-dashboard
Status: | Merged |
---|---|
Approved by: | Andy Doan |
Approved revision: | 694 |
Merged at revision: | 703 |
Proposed branch: | lp://staging/~doanac/qa-dashboard/live-status |
Merge into: | lp://staging/qa-dashboard |
Diff against target: |
392 lines (+328/-1) 5 files modified
qa_dashboard/settings.py (+13/-0) requirements.txt (+3/-0) smokeng/api.py (+119/-0) smokeng/tests.py (+188/-0) smokeng/urls.py (+5/-1) |
To merge this branch: | bzr merge lp://staging/~doanac/qa-dashboard/live-status |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Joe Talbott | Approve | ||
PS Jenkins bot | continuous-integration | Approve | |
Chris Johnston | Approve | ||
Andy Doan | Pending | ||
Review via email: mp+198602@code.staging.launchpad.net |
This proposal supersedes a proposal from 2013-11-21.
Commit message
Add a REST API to Smoke objects
Description of the change
Add a REST API to Smoke objects
This gives us the ability to have our jenkins jobs notify the
dashboard in realtime about smoke status and not have to wait
until the job has been pushed to the public server and then
polled by the pull-script.
In addition to a fairly thorough set of unit-tests, I've also
created a pretty easy CLI to do some exploratory testing with:
http://
That script will probably land in the lp:ubuntu-test-cases/touch repo
in some form or another.
Some notes to keep in mind:
* The API does not allow for delete operations (just to help decrease
the amount of damage someone might accidentally do).
* It doesn't require auth[entication
use's Django users + Tastypie ApiKey for PUT and PATCH operations.
* I had to use two hacks with Tastypie:
1) 0.9.15 because 0.10 migrations don't work with python 2.7 and
django 1.5
2) settings.US_TZ had to be enabled as noted in the settings.py
due to a tastypie bug.
I'm not really excited about #2, but given the limited use of "writes"
we have in the dashboard, I think this may be fairly safe/isolated.
wanted to share the branch, but I'd like to try and get one more unit test written to help make sure it plays nicely with the pull-script