On Fri, Jun 10, 2022 at 08:56:25AM +0200, Milan Crha wrote: > On Thu, 2022-06-09 at 12:48 -0700, Adam Williamson wrote: > > Currently this would usually mean a wait from update submission to > > 'stable push' (which really means that the build goes into the > > buildroot, and will go into the next Rawhide compose when it happens) > > of somewhere between 45 minutes and a couple of hours. > > Hi, > it is very convenient to `fedpkg chain-build ....` in the right order, > do it in fire & forget way, check the whole chain build task in koji > after some time and that's all. If it's going to take couple hours, the > koji build will surely timeout. > > I do the chain-build for stable branches too, just step in and set > overrides for the packages when needed. It might be an outdated > workflow, but it works for me for years. You can use chain-build with side tags just fine too. Just pass a --target fNN-build-side-XXXX No need for overrides. > I understand the side tags are here to help. That means to file the > update manually for rawhide, because the automatic updates won't make > it, right? It sounds like more work and time for the packagers. Perhaps we could enhance fedpkg chain-build to submit the update at the end if all the builds are successfull? Then you could just start the chain-build and if it all worked be done. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-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/desktop@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
