On Wed, 14 May 2014 16:38:50 +0200
Honza Horak <hhorak(a)redhat.com> wrote:
On 05/13/2014 03:02 PM, Marcela Mašláňová wrote:
> * ACTION: hhorak will ask Fedora QA about taskotron status
> (hhorak, 12:55:03)
I've just had a word with Kamil Dudka, one of the Taskotron
developers, and this is its current status:
I suspect that you meant Kamil Páral, no?
* taskotron will have the first release soon (days or weeks)
* it is already doing something (staging instance is running
somewhere, but there is no guarantee given on the functionality yet)
Links to the staging are as follows:
- results display (primitive yet, we know)
- task execution
At the moment, we're running rpmlint, upgradepath and a trivial example
task which runs on bodhi updates.
* it is theoretically possible to add some non-destructive tests
(features for running destructive tests in some isolated environment
are not ready yet), which could be enough for some RPM tests
(provides, requires, content)
* however, guys from Fedora QA are not very excited about adding
new things in this stage where the infrastructure for 3rd party tests
is still missing and adding something new would have to be hacked,
but I hope in case there is big-enough demand...
We haven't really come to a conclusion on what features we're going to
focus on after we reach the initial milestone of "autoqa replacement".
The only group that has reached out to us with a semi-concrete
proposal/plan so far is the cloud WG.
One of the primary limiting factors is that there are only so many of
us currently working on Taskotron. Folks willing to help add features
is a good way to get something done more quickly but a semi-concrete
"this is what we want to do" is a bare minimum.
* for Fedora 21 all current Fedora QA tests should be run by
taskotron (depcheck, rpmlint, upgradepath)
* results will be provided in Bodhi for start, the same as AutoQA
does it, before resultdb and/or fedmsg connection is ready
We're trying to limit the number of times that we change how packagers
are notified about results, so we'll using the same method for
notifications as AutoQA did for the immediate future.
* in case we have some other questions or some particular requests
to proceed some tests, Fedora QA mailing list or tflink (who cares
about deployment in Fedora QA) seem to be the best places to start
Almost all of the Taskotron development conversations have been on the
I'm also following this list and can answer questions about Taskotron.