Upload AzCopy binaries to Github #3014
Open
+31
−12
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
The previous step of uploading the binaries to blob storage account was more complex than necessary given that GitHub provides its own release functionalities. This change will streamline the binary distribution process. See doc below for more info
Switched over from uploading AzCopy binaries to a storage account to uploading them on GitHub as assets. Modified the 1ES release pipeline to include this.
Related Links:
Doc: Moving from blob origin to GitHub releases for AzCopy
[Email Subject] "Can we reduce SFI churn by moving to GitHub releases"
Type of Change
How Has This Been Tested?
Manually tested the binaries are uploaded under a new release.
Thank you for your contribution to AzCopy!