X Tutup
Skip to content

[release/v7.5]Deploy Box Update#24779

Merged
jshigetomi merged 1 commit intorelease/v7.5from
backport-24632-2
Jan 15, 2025
Merged

[release/v7.5]Deploy Box Update#24779
jshigetomi merged 1 commit intorelease/v7.5from
backport-24632-2

Conversation

@TravisEz13
Copy link
Copy Markdown
Member

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:

  • Replaced the DownloadPackages stage with setReleaseTagAndUploadTools and updated dependencies accordingly in .pipelines/PowerShell-Release-Official.yml. [1] [2] [3]

Dependency Updates:

  • Added a new repository PSInternalTools to the resources section in .pipelines/PowerShell-Release-Official.yml.
  • Introduced a new job SetTagAndTools in .pipelines/templates/release-SetTagAndTools.yml to set release tags, upload tools, and manage changelogs.

Variable Handling:

  • Updated variable setting commands to include isOutput=true for better output handling in .pipelines/templates/release-SetReleaseTagandContainerName.yml. [1] [2]
  • Added new parameters RELEASETAG and VERSION to .pipelines/templates/variable/release-shared.yml and updated related variables. [1] [2]

Artifact Management:

  • Updated artifact names and added new pipeline artifacts in .pipelines/templates/release-githubtasks.yml and .pipelines/templates/release-publish-nuget.yml. [1] [2]
  • Modified steps to copy and manage GitHub release files and NuGet packages in .pipelines/templates/uploadToAzure.yml.

Miscellaneous:

  • Refined the environment variable capturing and removed redundant tasks in .pipelines/templates/release-githubtasks.yml. [1] [2]

* 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
Copy link
Copy Markdown
Member Author

/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-CI-static-analysis, PSResourceGet ACR

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Jan 14, 2025
@jshigetomi jshigetomi merged commit aa8f9a3 into release/v7.5 Jan 15, 2025
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

microsoft-github-policy-service bot commented Jan 15, 2025

📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

X Tutup