Add support to generate workload manifest MSIs#7548
Merged
Conversation
Member
Author
|
@pjcollins this should unblock you for Android workloads once it's merged and Arcade completes its validation build |
marcpopMSFT
approved these changes
Jun 23, 2021
1 task
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 support for workload manifests MSI generation.
The manifest MSIs are different from the workload packs in that they support upgrades. Upgrade codes are stable based on platform and the SDK feature band targeted by the manifest, e.g. x86+6.0.100 or x64 + 6.0.400. Product Codes will be changed for each build, resulting in treating the update as a major upgrade. See this for more details.
The temporary manifests in the SDK will share the same keypath as the manifests produced by the new build task. This ensures proper component reference counting. However, because the files are plain text, the non-versioned file rules will apply during install/uninstall/repair.
The versioning of the MSI will be left to the owner based on the underlying build environment.