Not much is going on with blockerbugs for the
short term - we're waiting to see how f21 and/or fedora.next shape
out before working on any new features beyond the small changes
ready for review(tflink,
16:08:54)
Current Status and Plans - resultsdb and testdays(tflink, 16:19:33)
the reduced re-implementation for resultsdb is
up and running at
http://resultsdb.qa.fedoraproject.org/resultsdb(tflink,
16:21:57)
resultsdb browsing is available at:
http://resultsdb.qa.fedoraproject.org/resultsdb_frontend/(tflink,
16:22:22)
resultsdb API docs are at:
http://docs.resultsdb.apiary.io/(tflink,
16:22:45)
the new resultsdb is (comparing to the old
concept) quite simplified on the data level - we stripped all the
un-used tables from the old concept, and adapted the data to what we
actually used with the autoqa reporting(tflink,
16:28:11)
old and new resultsdb schema displayed at:
https://fedoraproject.org/wiki/AutoQA_resultsdb_schema(tflink,
16:29:18)
the testdays app is IMHO quite self-confined,
and I have no immediate goals for changing what it does (apart of
bug-fixes). This is because it's using the 'old' resultsdb, and
uses TurboGears2(tflink,
16:40:28)
The plans for the future are to re-write it
with Flask & New Resultsdb but it is (at the moment) quite
low-priority(tflink,
16:42:29)
the main support tools that we have are
phabricator (code review, issue tracking etc.) and buildbot (in
progress)/ jenkins (existing, not quite working) for ci(tflink,
16:47:03)
phabricator is deployed at
https://phab.qadevel.cloud.fedoraproject.org/(tflink,
16:47:22)
AGREED: As we have a
longer break between releases for now, automation is a higher
priority because it is more disruptive and needs to be done
soon(tflink,
17:16:42)
The hope was to have taskotron phase 0
(https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase_0:_Investigation_and_Preparation)
done by now(tflink,
17:30:47)
task description format was proposed and sent
out to qa-devel@. response has been mostly positive and it is ready
to start moving forward(tflink,
17:31:36)
initial fedmsg reliability investigation
indicates that it will be reliable enough to use for automation
scheduling but we should continue to keep an eye on it(tflink,
17:32:27)
there was a proof-of-concept system running in
the fedora cloud, but it seems to be having issues ATM(tflink,
17:37:54)
The big remaining task for phase 0 is
discussion/investigation into notifications(tflink,
17:39:25)
the proof-of-concept runner does work locally
and does produce output to the console, it can't report to resultsdb
(yet) and needs some refactoring(tflink,
17:40:29)
ACTION: tflink to
finish notificaitons email and send it out to qa-devel@(tflink,
17:42:28)
depcheck scenarios have been drafted up and
fake rpms have been coded up for testing(tflink,
17:45:34)