Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Make sure the vPack pipeline does not produce an empty package#24988

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

Merged
TravisEz13 merged 3 commits intoPowerShell:masterfromTravisEz13:fix-vPack
Feb 24, 2025

Conversation

TravisEz13
Copy link
Member

This pull request includes several changes to the.pipelines/PowerShell-vPack-Official.yml file to improve the handling of package artifacts and validation processes. The most important changes involve setting new package artifact variables, updating paths for artifact listings, and adding error handling for missing files.

Improvements to package artifact handling:

  • Updated the script to setPackageArtifactPath and included the corresponding variable in the pipeline.
  • Changed the path for capturing artifact listings to usePackageArtifactPath instead ofSystem.ArtifactsDirectory.

Validation and error handling enhancements:

  • Added error handling to throw an exception if no packages are found in the specified path.
  • Included a check to ensure that theob_outputDirectory contains files before proceeding, throwing an error if none are found.

Signing configuration update:

  • Modified thefiles_to_sign parameter to include onlySystem.Management.Automation.dll instead of all.dll and other file types.

Copy link
Contributor

@CopilotCopilotAI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

@TravisEz13
Copy link
MemberAuthor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

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

@TravisEz13TravisEz13 merged commit462585a intoPowerShell:masterFeb 24, 2025
36 checks passed
@TravisEz13TravisEz13 deleted the fix-vPack branchFebruary 24, 2025 18:30
@microsoft-github-policy-serviceMicrosoft GitHub Policy Service
Copy link
Contributor

microsoft-github-policy-servicebot commentedFeb 24, 2025•
edited by unfurl-linksbot
Loading

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

🔗https://aka.ms/PSRepoFeedback

@microsoft-github-policy-servicemicrosoft-github-policy-servicebot removed the Review - NeededThe PR is being reviewed labelFeb 24, 2025
TravisEz13 added a commit to TravisEz13/PowerShell that referenced this pull requestFeb 24, 2025
@adityapatwardhanadityapatwardhan added the CL-BuildPackagingIndicates that a PR should be marked as a build or packaging change in the Change Log labelMar 25, 2025
pwshBot pushed a commit to pwshBot/PowerShell that referenced this pull requestApr 11, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

Copilot code reviewCopilotCopilot left review comments

@adityapatwardhanadityapatwardhanadityapatwardhan approved these changes

@tgauthtgauthtgauth approved these changes

Assignees
No one assigned
Labels
BackPort-7.4.x-DoneBackPort-7.5.x-DoneCL-BuildPackagingIndicates that a PR should be marked as a build or packaging change in the Change LogMustHave
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@TravisEz13@adityapatwardhan@tgauth
[8]ページ先頭
©2009-2025 Movatter.jp