publish_release.py: upload archives to s3 #62
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Jfrog is deprecated. Here are other options:
AWS S3 is 10x cheaper than the most basic JFrog subscription. It adds a level of redundancy to safely keep a copy of the downloads.
Created S3 bucket "boost-archives".
Enabled versioning.
This pull request adds the feature to be able to upload archive bundles to S3 from
publish_release.py.When approaching the Jfrog end-of-life, change the various dryrun settings to enable S3 uploads, and also switch the "s3 website docs" dryrun setting so that it's based on the right variable.
In the meantime, archives should still be uploaded to S3. That's being done on brorigin1 in a cron, and so at the moment isn't needed in
publish_release.py.