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>
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 |
|
Pull request contains merge conflicts. |
Contributor
|
📣 Hey @TravisEz13, 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 changes to the PowerShell release pipeline to improve the tagging, tool uploading, and artifact handling processes. The most important changes include the addition of a new repository, restructuring of stages and jobs, and the introduction of output variables for better pipeline integration.
Pipeline Configuration Changes:
Added
PSInternalToolsrepository to theresourcessection in.pipelines/PowerShell-Release-Official.ymlto include internal tools.Replaced the
DownloadPackagesstage with a newsetReleaseTagAndUploadToolsstage, including a new job templaterelease-SetTagAndTools.yml. This change restructures the pipeline to set release tags and upload tools before proceeding with other stages. [1] [2] [3]Job and Step Modifications:
Updated the
release-SetReleaseTagandContainerName.ymltemplate to set output variablesOutputReleaseTagandOutputVersionfor better integration with subsequent steps. [1] [2]Introduced a new job
SetTagAndToolsin therelease-SetTagAndTools.ymltemplate to handle setting tags, uploading tools, and signing artifacts.Artifact and Variable Handling:
Modified the
release-githubtasks.ymlandrelease-publish-nuget.ymltemplates to use the new output variables for release tags and versions, ensuring consistent artifact naming and handling. [1] [2] [3] [4]Updated the
release-validate-packagenames.ymltemplate to use theOutputReleaseTagvariable for setting the release name.Miscellaneous Updates:
RELEASETAGandVERSIONto therelease-shared.ymlvariable template for better parameterization and default initialization. [1] [2]These changes collectively enhance the pipeline's efficiency, maintainability, and clarity by organizing stages, improving artifact management, and ensuring consistent variable usage.