#109: post-bodhi-update watcher
-----------------------+----------------------------------------------------
Reporter: wwoods | Owner: wwoods
Type: task | Status: assigned
Priority: major | Milestone: autoqa depcheck
Component: watchers | Version: 1.0
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment (by wwoods):
On further investigation, the 'list' call is working as we'd hoped - I was
just passing the timestamp in the wrong format.
There's now some very basic code in my git branch:
[
http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=hooks/post-bodhi-
update/watch-bodhi-
requests.py;h=f1c4010189dd391a0e4176f852c8e91f97307cfc;hb=wwoods watch-
bodhi-requests.py]
As discussed in ticket #87, though, there are some deficiencies in the
current bodhi model of update stages. For now it'll work like this:
1. This hook will trigger anytime a new update is created, and
1. For new critpath updates, we won't know whether they're going to
'testing' or 'stable', so we need to test against both.
Deciding what to do with the test results for critpath updates will
therefore be a little tricky, since we're going to have two sets of
(possibly-conflicting) results for each update.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/109#comment:5>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project