[release/v7.5]Deploy Box Update #24779
Merged
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
* reverted one time changes * added ob_outputDirectory * added mscode variable group * forgot to move psm1 to ToolArtifact folder * added pipeline name and passing toolartifact through context * added tools * PSPackagesOfficial * removed tools clone * added uploading CL * verbose statements for release tag and release version * trying to regerence variable with step name * checking REPOROOT * removed get child item * Deploy box update * nuget template context pipeline name correction * changed other instances of releasetag * added -Verbose to Copy-Item * checkout task, instead of git clone * changed to Build.SourcesDirectory * removed path specification * removed path * added tsa and credscan * not copying tools to artifacts * official and production --------- Co-authored-by: Justin Chung <chungjustin@microsoft.com> Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
TravisEz13
requested review from
adityapatwardhan,
anmenaga and
daxian-dbw
as code owners
Member
Author
|
/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-CI-static-analysis, PSResourceGet ACR |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
TravisEz13
added
the
CL-BuildPackaging
jshigetomi
approved these changes
Jan 15, 2025
Contributor
|
📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
21 tasks
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 #24632
This pull request includes significant updates to the PowerShell release pipeline. The changes focus on restructuring stages, updating dependencies, and refining variable handling to enhance the release process.
Pipeline Restructuring:
DownloadPackagesstage withsetReleaseTagAndUploadToolsand updated dependencies accordingly in.pipelines/PowerShell-Release-Official.yml. [1] [2] [3]Dependency Updates:
PSInternalToolsto theresourcessection in.pipelines/PowerShell-Release-Official.yml.SetTagAndToolsin.pipelines/templates/release-SetTagAndTools.ymlto set release tags, upload tools, and manage changelogs.Variable Handling:
isOutput=truefor better output handling in.pipelines/templates/release-SetReleaseTagandContainerName.yml. [1] [2]RELEASETAGandVERSIONto.pipelines/templates/variable/release-shared.ymland updated related variables. [1] [2]Artifact Management:
.pipelines/templates/release-githubtasks.ymland.pipelines/templates/release-publish-nuget.yml. [1] [2].pipelines/templates/uploadToAzure.yml.Miscellaneous:
.pipelines/templates/release-githubtasks.yml. [1] [2]