Skip to content
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

[Release/5.0] - Fix versions for Libs native artifacts #53000

Merged
merged 2 commits into from
Jun 3, 2021

Conversation

janvorli
Copy link
Member

Port of #52799 and #52917

During the repo consolidation, we missed passing OfficialBuildId
argument to common script from all subsets, which resulted in default
version emitted in the binaries produced by Libs subset in the official
builds.

Customer Impact

Version of libraries native binaries cannot be figured out.

Testing

Built libraries and manually checked that the build Id is there.

Risk

Low, it only adds the missing embedded version hash / official version number to the binaries.

Regression

Yes, it was ok in 3.1, got broken during repo consolidation.

Port of dotnet#52799 and dotnet#52917

During the repo consolidation, we missed passing OfficialBuildId
argument to common script from all subsets, which resulted in default
version emitted in the binaries produced by Libs subset in the official
builds.
@janvorli janvorli added the Servicing-consider Issue for next servicing release review label May 19, 2021
@janvorli janvorli added this to the 5.0.x milestone May 19, 2021
@janvorli janvorli requested a review from ViktorHofer May 19, 2021 23:15
@janvorli janvorli self-assigned this May 19, 2021
@ghost
Copy link

ghost commented May 19, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Port of #52799 and #52917

During the repo consolidation, we missed passing OfficialBuildId
argument to common script from all subsets, which resulted in default
version emitted in the binaries produced by Libs subset in the official
builds.

Customer Impact

Version of libraries native binaries cannot be figured out.

Testing

Built libraries and manually checked that the build Id is there.

Risk

Low, it only adds the missing embedded version hash / official version number to the binaries.

Regression

Yes, it was ok in 3.1, got broken during repo consolidation.

Author: janvorli
Assignees: janvorli
Labels:

Servicing-consider, area-Infrastructure-libraries

Milestone: 5.0.x

@ghost ghost added this to In Progress in Infrastructure Backlog May 19, 2021
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. We should consider this for 5.0.x to aid in post mortem diagnostics

@am11
Copy link
Member

am11 commented May 20, 2021

@janvorli thank you. Could you please add ebdcb5e and 78372a0. Former will ensure we have version/commit info in singlefilehost as well, and the latter was a fix for wasm-on-windows (conditionally augment OfficialBuildId).

@janvorli
Copy link
Member Author

@am11 the singlefilehost was already ok, I guess it got broken in 6.0 branch by the versioning changes there. As for the other commit, I've already incorporated the quoting there. So this change results in everything having the right version and nothing being broken.

@janvorli
Copy link
Member Author

@am11, ah, I can see that I've not added the check for empty version id that was the other commit you've mentioned.

@leecow leecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels May 25, 2021
@leecow leecow modified the milestones: 5.0.x, 5.0.8 May 25, 2021
@Anipik Anipik merged commit e917853 into dotnet:release/5.0 Jun 3, 2021
Infrastructure Backlog automation moved this from In Progress to Done Jun 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants