- Notifications
You must be signed in to change notification settings - Fork7.7k
[release/v7.4]Deploy Box Update#24802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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>
/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. |
a022fae
intorelease/v7.4Uh oh!
There was an error while loading.Please reload this page.
microsoft-github-policy-servicebot commentedJan 16, 2025 • edited by unfurl-linksbot
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by unfurl-linksbot
Uh oh!
There was an error while loading.Please reload this page.
📣 Hey@TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗https://aka.ms/PSRepoFeedback |
Uh oh!
There was an error while loading.Please reload this page.
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 repositoryPSInternalTools
and 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 jobSetTagAndTools
to 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.