search

fedora-copr / copr

RPM build system - upstream for https://copr.fedorainfracloud.org/
115 stars 61 forks source link

AWS EC2 CloudFront confuses users - If results directory is opened mid-build, the build artifacts never appear #2169

Open fedora-copr-github-bot opened 1 year ago

fedora-copr-github-bot commented 1 year ago

Original issue: https://pagure.io/copr/copr/issue/2169 Opened: 2022-04-11 20:21:42 Opened by: salimma

Case in point: https://copr.fedorainfracloud.org/coprs/salimma/nu-wip/build/4179419/

I opened the fedora-rawhide-x86_64 directory mid-build: https://download.copr.fedorainfracloud.org/results/salimma/nu-wip/fedora-rawhide-x86_64/04179419-rust-imbl/

and now after the build is finished, it still contains only backend.log, build.info, and builder-live.log

praiskup commented at 2022-04-12 08:03:53:

We have docs for this, it is just a confusing behavior: https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded-but-i-don-t-see-the-built-results

We should tweak the Lighttpd cache behavior in those directories that are subject of changing.

praiskup commented 1 year ago

Triage time: @xsuchy proposes a cache invalidation

gstrauss commented 1 year ago

2011 dates back to https://pagure.io/copr/copr/issue/2001 almost 15 months ago and contains numerous suggestions for improving the service, along with code to do so.

gstrauss commented 1 year ago

https://github.com/fedora-copr/copr/issues/2011 dates back to https://pagure.io/copr/copr/issue/2001 over 16 months ago and contains numerous suggestions for improving the service, along with step-wise incremental code steps to do so.

gstrauss commented 10 months ago

https://github.com/fedora-copr/copr/issues/2011 dates back to https://pagure.io/copr/copr/issue/2001 almost 2 years ago (!) and contains numerous suggestions for improving the service, along with step-wise incremental code steps to do so.