On Mon, Jun 20, 2022 at 09:47:27PM +0200, Zbigniew Jędrzejewski-Szmek wrote: > > Official non-scratch builds for non-merged pull requests? Looks very > > dangerous. > > Yeah. I think we should think about scratch and non-scratch builds > separately. For scratch builds, e.g. in a pull request, it's just fine > to do repeated builds with the same NEVR. For non-scratch builds, the > fact that you cannot do that is a feature. The advantage I see in the proposal is that the final build gets promoted, so you have an artifact which has, theoretically at least, been under scrutiny, rather than a new one which we _hope_ is the same. But I'm not sure that really buys us a lot in quality, since the build environment updates. If promoting the scratch build avoids a problem that would have happened if it were rebuilt... well, that problem is going to come up later during a mass or automatic rebuild later anyway. It does, of course, reduce extraneous throw-away computing. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ 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
