On Tue, Jan 21, 2025 at 03:42:22PM +0100, Miroslav Suchý wrote: > Dne 21. 01. 25 v 3:13 odp. Zbigniew Jędrzejewski-Szmek napsal(a): > > At the fundamental level, such automation would effectively do two > > steps: > > 1. create a no-change commit like we do now, > > 2. push the commit and fire off a build. > > Packit team want to do this for some time. Unfortunately, it did not propagated on top of priorities yet. > > > I would love to see automation that'd allow me to request a build > > when the commit reaches a branch. > > Such automation already exists and is heavily used by many: > > https://packit.dev/docs/configuration/downstream/koji_build#example Yeah, but in this form, this only works for projects where the decision whether to do a build is completely static. I think this is fundamentally the bad choice to apply such static config: the decision whether to make the build is *per-commit*. Sometimes I want to do an update immediately, sometimes I want to push some changes but then merge some outstanding PRs, sometimes I plan to do a side-tag build, etc. In fact, if we have the system where you can specify whether to do a build automatically for a given commit, then the whole system of configuring whose commits should trigger a rebuild goes away and is replaced by a much simpler system: - if a build was requested, if the person who pushed the commit is allowed to do a build for the package, do the build, otherwise don't. Zbyszek -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
