On Fri, Nov 12, 2021 at 10:06 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On Wed, Nov 10, 2021 at 09:47:47AM +0100, Florian Weimer wrote: > > * Kevin Fenzi: > > > > > On Tue, Nov 09, 2021 at 10:41:16AM +0100, Florian Weimer wrote: > > >> * Kevin Fenzi: > > >> > > >> > Isn't this an ideal use case for copr? > > >> > > >> I don't know. I could piece together the Koji API fairly easily, and > > >> had hoped to reuse some of the script logic. > > >> > > >> Or does COPR have direct support this? Can I tell it directly to report > > >> rawhide in a special buildroot? Is there a programmatic way to access > > >> the resulting log files? > > >> > > >> (I won't need the built RPMs, which is why I would use scratch builds in > > >> Koji.) > > > > > > Yes, copr has a api also. > > > https://python-copr.readthedocs.io/en/latest/ClientV3.html > > > > Is there an overview similar to <https://koji.fedoraproject.org/koji/api>? > > It's hard to tell what the capbilities are. > > I'm not sure and I was hoping one of the copr folks would chime in. ;) > > CCing praiskup I'm pretty sure the Python team is doing something very similar for their Python, Sphinx, etc. rebase test build COPRs, like this one for Python 3.10: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/ They're set up so that any dist-git commits (and PRs) are automatically rebuilt in that COPR. The COPR command-line tool (copr-cli) provides all commands that are needed to set that up, as far as I know - so the copr python module should do that, too. Fabio _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
