Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@TravisEz13
Copy link
Member

Backport #24988

This pull request includes several important changes to the .pipelines/PowerShell-vPack-Official.yml file to improve the handling of package artifacts and ensure proper validation and signing of files. The key changes involve setting new variables, updating paths, adding error handling, and refining file selection for signing.

Improvements to package artifact handling:

  • Added a new variable PackageArtifactPath and updated commands to use this variable instead of System.ArtifactsDirectory. This change ensures that the correct path is used consistently throughout the pipeline.
  • Included error handling to throw an exception if no packages are found in the specified path, improving the robustness of the pipeline. [1] [2]

Validation and signing refinements:

  • Modified the file selection pattern for signing to include only System.Management.Automation.dll and exclude other .dll and script files. This change ensures that only the necessary files are signed.
  • Updated the validation step to focus on .zip packages and ensure that the correct architecture is used. This change helps in maintaining the integrity of the package validation process.

@TravisEz13
Copy link
Member Author

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

@azure-pipelines
Copy link

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

@TravisEz13 TravisEz13 merged commit 7121cd4 into PowerShell:release/v7.4 Feb 24, 2025
31 checks passed
@TravisEz13 TravisEz13 deleted the backport-24988-748 branch February 24, 2025 22:56
@microsoft-github-policy-service
Copy link
Contributor

microsoft-github-policy-service bot commented Feb 24, 2025

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

🔗 https://aka.ms/PSRepoFeedback

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Feb 25, 2025
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