[release/v7.5]Deploy Box Update - #24665
Closed
Justin Chung (jshigetomi) wants to merge 1 commit into
Closed
Conversation
* 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>
Justin Chung (jshigetomi)
marked this pull request as ready for review
December 12, 2024 19:23
Contributor
|
📣 Hey @Justin Chung (@jshigetomi), how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
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.
Backport #24632
This pull request includes significant updates to the PowerShell release pipeline, focusing on restructuring stages and jobs, improving variable handling, and enhancing artifact management.
Pipeline restructuring and job updates:
.pipelines/PowerShell-Release-Official.yml: Added a newsetReleaseTagAndUploadToolsstage to replace theDownloadPackagesstage, and updated dependencies and templates accordingly. [1] [2] [3].pipelines/templates/release-SetTagAndTools.yml: Introduced a new job for setting release tags and uploading tools, including steps for signing tools and uploading changelogs.Variable handling improvements:
.pipelines/templates/release-SetReleaseTagandContainerName.yml: Updated thevstsCommandStringto includeisOutput=truefor better output management. [1] [2].pipelines/templates/variable/release-shared.yml: Added new parametersRELEASETAGandVERSIONand corresponding variables to manage release tags and versions. [1] [2]Artifact management enhancements:
.pipelines/templates/release-githubtasks.yml: Updated artifact names and added steps to capture environment variables and manage GitHub release files. [1] [2] [3].pipelines/templates/release-publish-nuget.yml: Updated artifact names and parameters for version management..pipelines/templates/uploadToAzure.yml: Re-enabled and updated the script for copying GitHub release files and NuGet packages to the artifacts directory.