davsclaus opened a new pull request, #1633: URL: https://github.com/apache/camel-website/pull/1633
## Summary - Use `rsync` instead of `git rm -r * && cp -R` in the deploy stage so git only sees actually-changed files rather than marking all ~15,000+ files as changed on every build - Add a follow-up empty "nudge" commit + push after the main deploy to reliably trigger CDN cache purge ## Why Per [INFRA-27679](https://issues.apache.org/jira/browse/INFRA-27679), the ASF message queue has a **256KB event payload limit**. Large pushes with 15,000+ changed files exceed this limit, causing the CDN PURGE request to be **silently dropped**. The CDN then serves stale content (including cached 404s) indefinitely. The `rsync --delete` approach only produces git diffs for files that actually changed. A blog-only update might change 10 files instead of 15,000, staying well within the 256KB payload limit. The follow-up nudge push (after a 5-second delay) provides a safety net: even if the main push exceeds the limit, this tiny second push will trigger the CDN purge. ## Test plan - [ ] Verify rsync is available in the Jenkins Docker build environment - [ ] Test that `.asf.yaml` is still correctly restored from `$VALID_ASF_YAML` - [ ] Confirm the nudge push triggers CDN cache invalidation - [ ] Monitor next deploy for 404 recurrence Fixes #1631 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
