#109: post-bodhi-update watcher ----------------------+----------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- the post-bodhi-update hook (see ticket #87) will require a post-bodhi- update watcher. This should use the bodhi API to get info about newly- created/changed updates and fire tests.
#109: post-bodhi-update watcher -----------------------+---------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by wwoods):
python fedora provides a {{{fedora.client.bodhi}}} module, which has a {{{BodhiClient}}} class, so that's nice and easy. Unfortunately the .query() method does not provide a good way for us to list updates created/modified since a certain timestmp. This functionality will be added to Bodhi Real Soon Now.
In the meantime we can probably just look at all the latest updates and filter out the ones we've seen before.
#109: post-bodhi-update watcher -----------------------+---------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Resolution: | Keywords: -----------------------+---------------------------------------------------- Changes (by alexlan):
* cc: alexlan (added)
#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: -----------------------+---------------------------------------------------- Changes (by wwoods):
* owner: => wwoods * status: new => assigned
Comment:
As mentioned elsewhere, this is in progress. No code has been checked into git yet, though.
#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):
At some point lmacken and I discussed (and lmacken implemented) a 'start_date' parameter to the 'list' call. This would allow you to list pending releases newer than a given timestamp, e.g.:
{{{ def bodhi_pending_since(release, timestamp): bodhi = fedora.client.bodhi.BodhiClient() # start_date and end_date are undocumented arguments to bodhi's list call params = {'release': release, 'status': 'pending', 'start_date': timestamp} return bodhi.send_request('list', req_params = params) }}}
But it seems to be broken at the moment. Will investigate further.
#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.
#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):
With those caveats, we can probably have this hook fully functional given a week or two to work on it.
#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):
watcher is complete and seems to work as expected.
#109: post-bodhi-update watcher -----------------------+---------------------------------------------------- Reporter: wwoods | Owner: wwoods Type: task | Status: closed Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by wwoods):
* status: assigned => closed * resolution: => fixed
Comment:
Watcher and hook are merged into master.
autoqa-devel@lists.fedorahosted.org