only rely on brorigin1, brorigin2 to store the files. Or,
replace jfrog with an S3 bucket
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.
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.