-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use rclone instead of custom sync script to publish documentation to AWS S3 bucket #15155
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's brilliant, nice work!
Pull Request Test Coverage Report for Build 13326611785Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Stupid question, is it important to pass |
DNSdist CI failure is unrelated, see #15156 |
fi | ||
# Cleanup credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the VM gets destroyed right after this anyway, but it can't hurt
Short description
Publishing documentation to AWS S3 has been slow, likely due to the custom publish.js script overwriting all files. This patch uses rclone instead, which uses digests to figure out which files to actually upload. This also means we don't have to use the javascript script anymore and don't need to install all the node dependencies for the aws sdk, which will likely also save time.
Checklist
I have: