[release/v7.4]Fixed release pipeline errors and switched to KS3 #24816
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
* Fixed an error in the release pipeline * Fixed ReleaseTag and Version variable in validate packages * Switched from Netlock to KS3 --------- Co-authored-by: Justin Chung <[email protected]>
TravisEz13
requested review from
daxian-dbw,
adityapatwardhan and
anmenaga
as code owners
|
/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-CI-static-analysis, PSResourceGet ACR, PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
adityapatwardhan
approved these changes
Jan 17, 2025
|
📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
21 tasks
jshigetomi
added
BackPort-7.4.x-Done
BackPort-7.5.x-Done
CL-BuildPackaging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport #24751
This pull request includes several updates to various pipeline template files to ensure consistent use of output variables and improve the clarity and accuracy of the release process.
Updates to pipeline templates:
.pipelines/PowerShell-Release-Official.yml: Updated theWindowsHostVersionsection to specifyVersion: 2022and changed the network toKS3..pipelines/templates/release-SetReleaseTagandContainerName.yml: Modified the script to use$(OutputReleaseTag.ReleaseTag)instead of$(ReleaseTag)for setting theAzureVersionandVersionvariables..pipelines/templates/release-create-msix.yml: Changed the container name to use$(OutputVersion.AzureVersion)instead of$(AzureVersion)..pipelines/templates/release-githubtasks.yml: Added a new line to extract the release version from$(ReleaseTag)by removing the leading 'v'..pipelines/templates/release-validate-globaltools.yml: Updated the commands to use$(OutputVersion.Version)instead of$(Version)for tool installation and version validation. [1] [2].pipelines/templates/release-validate-packagenames.yml: Changed the container variable to use$(OutputVersion.AzureVersion)instead of$(AzureVersion)..pipelines/templates/release-validate-sdk.yml: Updated the release version variable to use$(OutputVersion.Version)instead of$(Version).