On Tue, Dec 22, 2020 at 11:15:53AM +0100, Miro Hrončok wrote: > On 21. 12. 20 19:36, Kevin Fenzi wrote: > > On Thu, Dec 17, 2020 at 09:21:15PM +0100, Fabio Valentini wrote: > > > As Miro mentioned, I've also developed scripts to handle this "does > > > this update break anything" for the Stewardship / Java SIG, because - > > > at least at first - we didn't have big enough egos / enough confidence > > > to just push updates to rawhide without testing excessively them > > > first: > > > https://github.com/fedora-stewardship/fedora-stewardship.github.io/blob/master/scripts/review_pr.py > > > > > > This first builds (one or more) packages from src.fpo dist-git forks > > > that were prepared for PRs in COPR, recursively or non-recursively > > > queries dependent packages for all of them, and rebuilds them in COPR. > > > Assuming that there's a copr-cli command for querying build successes, > > > they could be compared with the latest status of those packages in > > > koschei, and have it print new build failures. Right now, I compare > > > the results manually. > > > > > > Would something like this fit your definition of "does-it-blend" script? > > > > What format is '--from-git' in? Say I have a fork with a branch I want > > to test, what do I pass it? > > --from-git is a regex of package names that are built from dist git instead > of from latest known SRPM. > > AFAIK The script only supports "the one package" (that is being tested) to > be built from a custom branch, whoch is the purpose of the script: > > $ python scripts/review_pr.py foobar-2.0 kevin:foobar:branch-2.0 > > But you can later built another package in there (with or without depndents) > in the same copr: > > $ python scripts/review_pr.py foobar-2.0 kevin:bazbaz:fix_deps [-nx'.*'] Cool. The help didn't get me this at all. ;) --from-git FROM_GIT regexes for packages to build from git Perhaps that should be "copr-name packager-name:packagename:branchname" ? Anyhow, after that I ran it on python-dogpile-cache 1.1.1 upgrade: https://copr.fedorainfracloud.org/coprs/kevin/python-dogpile-cache-1.1.1/packages/ Cool. Of course there's still stuff to figure out, like: * Since this is a python-package, how many of those actually change on building against the newer package? I mean, can we tell in a scripted way how many packages just keep working fine with the new package and how many need to actually be rebuilt? * as you noted it would be nice to have some way to say 'package X failed to build against your change, but it's already failing to build and this isn't your fault/problem' It would be nice to modernize the fedora-packager package to include scripts like this and docs and make them nice. :) In any case thanks much for the script and pointers! kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
