Re: AutoQA PUAP check-in
Howdy folks,
My action items from our last meeting were pretty basic compared to post-bodhi-update,
virt-support and resultsdb:
* [jlaska] find a machine where resultdb may run (it can be VM, publicly
accessible preferred)
* [jlaska] set up testing instance of autotest-server
I believe we should be good to go on both the tasks above. I took the second task as an
opportunity to tackle ticket#188 and update our autotest to the latest upstream 0.12.0.
The autoqa (master+wwoods branch) and autotest-0.12.0-1 that Kamil is using are the
lastest builds. I can do another autoqa build now that the master branch has been
updated.
Thanks to the infrastructure team, http://autoqa.fedoraproject.org is coming along nicely.
That system is an EL5 xen guest, and smooge created the necessary mysql databases for us
on Friday. I'd like to deploy the latest autoqa+autotest packages on that system and
move our current "production" instance to autoqa.fedoraproject.org within the
next 2 weeks.
Thanks,
James
----- "Josef Skladanka" <jskladan(a)redhat.com> wrote:
Hello gang!
i started to work on a library, which wraps the usage of xmlrpc
resultsdb interface, so we can easily use it from inside the tests. I
also rewrote the initscripts test so it stores data in resultsdb via
this interface. I'll edit more of the tests next week. You can find
these changes in jskladan branch.
Next, I'd like to push this chaged version to the testing machine
kparal
uses for experimenting with autotest, so it can actually gather some
data into the resultsdb, and we can start creating some frontend.
Cheers
joza
_______________________________________________
autoqa-devel mailing list
autoqa-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/autoqa-devel