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
build: change upload-to-s3 vars to upload-to-storage #34105
Conversation
b304471
to
1accc24
Compare
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.
overall this PR is fine but @MarshallOfSound discovered an issue where usingupload-to-s3
causes overwriting the headers tarballs of legit releases. @MarshallOfSound's suggestion was that this flag should upload to a different container to prevent contention.
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.
disregard that last comment. However in a future PR we should update upload-to-storage
to exercise all upload paths (right now it skips some) and upload to an alternate container. But that is not a blocker for this PR.
No Release Notes |
I have automatically backported this PR to "15-x-y", please check out #34142 |
I have automatically backported this PR to "19-x-y", please check out #34143 |
I have automatically backported this PR to "17-x-y", please check out #34144 |
I have automatically backported this PR to "16-x-y", please check out #34145 |
I have automatically backported this PR to "18-x-y", please check out #34146 |
* build: change upload-to-s3 vars to upload-to-az * build: change upload-to-az to upload-to-storage
Description of Change
A follow up to #34104, this PR changes all instances of
upload-to-s3
toupload-to-storage
. We now use Azure, and this variable is now platform agnostic, should we want to switch platforms in the future.Please do not merge until the first PR is merged, and all instances of this variable have been confirmed changed in CircleCI and AppVeyor.This PR is ready for review. I checked both Appveyor and CircleCI, and neither appears to be storing a default value for UPLOAD_TO_S3. Since both already contain the necessary info for Azure, I think this should "just work".
Checklist
npm test
passesRelease Notes
Notes: no-notes