----- Original Message -----
From: "Jeremy Cline" <jeremy(a)jcline.org>
Sent: Tuesday, December 20, 2016 8:07:55 PM
Subject: Enabling "new koji build" Taskotron checks on scratch builds
I recently started maintaining the-new-hotness. In case anyone isn't
familiar with it, it's responsible for filing bugs when a new
release is made upstream. One of its components, rebase-helper,
currently tries to run a set of tests on packages when upstream
releases a new version.
There are a lot of problems with this process and for the most part it
does not work. I started a discussion on the issue tracker about
removing rebase-helper as a dependency. Kamil Páral mentioned that
there has been discussion about running the "new koji build" Taskotron
checks for scratch builds. This would be great for the-new-hotness since
it would do everything and more that rebase-helper currently does with
respect to testing.
How do people feel about this? Are there any obstacles?
I am not aware of any obstacles. To enable this we only need to push a
change into Taskotron Trigger that would listen on the koji scratch
fedmsgs and then wire your task to it. We can start in our dev instance
and see how it goes from there. Let us know if you need any help
with the "the-new-hotness" task.
Any objections/ideas/obstacles, folks?
>  https://github.com/fedora-infra/the-new-hotness/
>  https://bugzilla.redhat.com/show_bug.cgi?id=1404680
>  https://github.com/fedora-infra/the-new-hotness/issues/145
> Jeremy Cline
> XMPP: jeremy(a)jcline.org
> IRC: jcline
> qa-devel mailing list -- qa-devel(a)lists.fedoraproject.org
> To unsubscribe send an email to qa-devel-leave(a)lists.fedoraproject.org