From fedora-devel mailing list:
I would be very interested in feature, which instead of mock, will run Koji scratch build and then will download resulting packages from Koji. I have been thinking about this but as an option which would not be the default (imho).
As of now, using Koji becomes kind of a wrapper for fedora-review --name xxxx --prebuilt. It also has the same limitations since f-r in this case doesn't have access the BUILD directories.
Basically, this could be handled by a section in the manpage.
Pushed a feauture branch 'koji' which basically just updates the manpage with a workflow and adds a python script to download scratch builds from koji build server.
The workflow could be much more automated using the python interfaces in koji. Even so, this is a beginning.
Released 0.2.2 as of comment:4. Basically, this makes it possible to use koji, although it's not that automated. Setting priority to minor, since it actually works although manual.
Certainly something I want to finish up. But I want to release 0.3.0 ASAP, so pushing this to 0.3.1
fedora-review could use the koji build of fedora-create-review...
This would be nice, since a koji scratch build will be able to test the package build on all architectures. When using the mock build, all arches are not tested. So, I just did a review where the package built on my system (x86_64) using Fedora-review also, but when it was built on koji, it failed on arm/aarch64 and so on. Using koji scratch builds instead of mock would catch that.
Login to comment on this ticket.