For a while now, Fedora Quality Assurance (QA) is busy with building Taskotron core features and didn’t have resources for additions to tasks that Taskotron runs. That changed a few weeks back when we started running task-dockerautotest, task-abicheck and task-rpmgrill tasks in our development environment. Since then, we are happy with the results of those tasks. We deployed them to the production instance last week. Please note that the results of those tasks are informative only. Let’s introduce the tasks briefly.
task-dockerautotest is the first package-specific task that Taskotron runs. It triggers on each completed Docker build in Koji. Please note that we wrote only the Taskotron wrapper for the dockerautotest test suite. The test suite’s git repository is found here and the task’s git repository here.
task-abicheck looks for incompatibilities in ABI between two versions of a package. The task runs only on a subset of packages in Fedora. Currently, we run the task on a subset (excluding
qt) of packages from critpath. For now, the reason we limit packages we run the task on is due to memory consumption the task needs for some packages. Each time a build of a package from critpath completes in Koji, task-abicheck runs and compares ABIs of the build and its earlier version. Kudos to Dodji Seketeli for the work on libabigail and Sinny Kumari for writing the task! The task’s git repository is found on pagure.
task-rpmgrill runs each time a build completes in Koji. It performs a set of analysis tests on all RPMs built from the build’s source RPM. The task expands capabilities of task-rpmlint with build log analysis or ELF checks, to name a few. Kudos to Ralph Bean for writing Taskotron wrapper for the task! The task’s git repository is found here.
Looking at the task results
Interested in looking at the new tasks results? You can do so via ResultsDB frontend.
Taskotron’s glorious future
Recently, Miro Hroncok sent a review request for “Python Version Check” which we are planning to check and deploy in the not so distant future. We are also looking for “guinea pigs” to write package-specific tasks so we can test our upcoming feature, dist-git style tasks. If you have a task (or an idea of), either generic or packages-specific and want to run it in Taskotron, please do reach to us.
Receiving notifications about results
If you wish to receive notifications about any of new tasks results of you package, you can do so in FMN. If you are not sure how to set up notifications, my earlier post on that topic should help with that.
Found an issue?
As usual, if you hit any issues and/or have any questions or suggestions, don’t hesitate to contact us either in #fedora-qa on Freenode IRC or on qa-devel mailing list. You can also file bugs or send RFE in our Phabricator instance.