[release/v7.4]Deploy Box Update#24802
Merged
Merged
[release/v7.4]Deploy Box Update#24802
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>
Member
Author
|
/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. |
jshigetomi
approved these changes
Jan 16, 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
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 several changes to the PowerShell release pipeline configuration to improve the release process and ensure proper handling of artifacts and versioning. The most important changes include adding new stages and jobs, modifying existing jobs to use outputs as inputs, and updating variable management.
Enhancements to the release pipeline:
.pipelines/PowerShell-Release-Official.yml: Added a new repositoryPSInternalToolsand introduced multiple new stages includingsetReleaseTagAndUploadTools,PublishGitHubRelease, andPushGitTagAndMakeDraftPublic. These changes improve the release tagging and artifact upload processes. [1] [2] [3] [4].pipelines/templates/release-SetReleaseTagandContainerName.yml: Updated the script to set release tag and container name as output variables, and added names to the steps for better traceability. [1] [2].pipelines/templates/release-SetTagAndTools.yml: Added a new jobSetTagAndToolsto handle setting the release tag, signing tools, and uploading the changelog. This job ensures that the necessary tools and changelog are correctly prepared and uploaded..pipelines/templates/release-githubtasks.yml: Modified the job to use the new output variables and improved the handling of GitHub release tasks by using a more structured approach to manage artifacts and environment variables. [1] [2] [3].pipelines/templates/release-publish-nuget.yml: Updated the job to use the new output version variable and improved the process for capturing environment variables and handling NuGet packages. [1] [2]These changes collectively enhance the robustness and traceability of the release pipeline, ensuring a smoother and more reliable release process.