Ci/deploy website using hugo deploy #623
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Note
Previews will not work in this PR, because preview workflows have been updated here.
This PR improves the website deployment strategy for PR previews on GitHub:
pr-build-previewused to build the website on the fork side. Then it triggered the workflowprw-deploy-previewon the upstream repo side. The build files were passed via artifacts which took more time.aws s3was used for deployment with custom logic to prevent re-uploading unchanged files (ci: optimize file syncing with s3 #381).pr-trigger-previewcollects the PR details on the fork side. Then it triggered the workflowprw-deploy-previewon the upstream repo side. The website build and deploy is done in the same workflow. File syncing is managed by Hugo much more efficiently.Key improvements:
aws-cliit took around 4 minutes.Follow-up actions
Once we make sure that this workflow works file, we will reuse it for the production environment.
Related
Testing
Thorough testing was done in PR #22
Checklist
Before submitting a Pull Request, please ensure the following: