Add release builds that produce symbols for compliance scans #5086
Conversation
This file contains hidden or 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
adityapatwardhan
approved these changes
Oct 11, 2017
Member
adityapatwardhan
left a comment
adityapatwardhan
left a comment
There was a problem hiding this comment.
LGTM with minor comment
Member
Author
|
This is needed to finish high-priority work. I will merge when tests finish. |
TravisEz13
force-pushed
the
UpdateReleaseBuildToSupportAPIScan
branch
from
d7e7877 to
64de607
Compare
Member
Author
|
rebased so I can test with other changes. |
daxian-dbw
approved these changes
Oct 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add two new named release builds that produce zip files with symbols.
update the infrastructure to support these builds.
Add a readme to describe how to use the release builds.