fedora-ci / general

#493 Cancel scratch builds on PR update
Opened by nikic. Modified

Open
Close Issue

It looks like currently old scratch builds keep running even if a PR is updated. If there are many PR updates in a short time on a package with long build times, this can cause a lot of load on koji. This was pointed out in https://src.fedoraproject.org/rpms/llvm/pull-request/301.

There is also the additional issue that scratch builds are duplicated between Fedora CI and Zuul, but I think this is already tracked at https://pagure.io/fedora-ci/general/issue/476.

To gather some thoughts on what we would need to achieve this. I believe for zuul this would be setting job.post-run.cleanup, for jenkins runs I believe it would be post: aborted

Thank you for working on this or at least thinking about this. I think the effort is worth it given the amount of build time that we produce in the background when updating PRs.

Thank you for working on this or at least thinking about this. I think the effort is worth it given the amount of build time that we produce in the background when updating PRs.

My thoughts exactly. We are also in the fun position where we are making room for the 3rd CI infrastructure, and it's the beta freeze period, quite the busy period all-around
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.