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

[release/v7.4]Add a parameter that skips verify packages step#24803

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 2 commits intorelease/v7.4frombackport-24763-74
Jan 16, 2025

Conversation

TravisEz13
Copy link
Member

Backport#24763

This pull request includes changes to the.pipelines/apiscan-gen-notice.yml and.pipelines/templates/compliance/generateNotice.yml files to introduce new parameters and improve the flexibility of the pipeline configuration. The most important changes include adding new parameters for debugging and skipping package verification, and modifying job conditions based on these parameters.

Pipeline configuration improvements:

  • AddedFORCE_CODEQL andSkipVerifyPackages parameters to.pipelines/apiscan-gen-notice.yml for debugging and skipping package verification.
  • Modified theextends: section in.pipelines/apiscan-gen-notice.yml to pass theSkipVerifyPackages parameter to the compliance template.

Compliance template updates:

  • AddedSkipVerifyPackages parameter to.pipelines/templates/compliance/generateNotice.yml.
  • Updated job conditions in.pipelines/templates/compliance/generateNotice.yml to skip package verification ifSkipVerifyPackages is set to true.
  • Cleaned up comments and formatting in.pipelines/templates/compliance/generateNotice.yml.

* added a parameter that skips verify packages step* fix parameter string to boolean value---------Co-authored-by: Justin Chung <chungjustin@microsoft.com>
@TravisEz13
Copy link
MemberAuthor

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

@azure-pipelinesAzure Pipelines
Copy link

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

@TravisEz13TravisEz13 added the CL-BuildPackagingIndicates that a PR should be marked as a build or packaging change in the Change Log labelJan 16, 2025
@TravisEz13TravisEz13 merged commit8d74036 intorelease/v7.4Jan 16, 2025
8 checks passed
@TravisEz13TravisEz13 deleted the backport-24763-74 branchJanuary 16, 2025 23:53
@microsoft-github-policy-serviceMicrosoft GitHub Policy Service
Copy link
Contributor

microsoft-github-policy-servicebot commentedJan 16, 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

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

@adityapatwardhanadityapatwardhanadityapatwardhan approved these changes

@daxian-dbwdaxian-dbwAwaiting requested review from daxian-dbw

@anmenagaanmenagaAwaiting requested review from anmenaga

Assignees
No one assigned
Labels
CL-BuildPackagingIndicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

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