Create new pipeline for compliance #24252
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adityapatwardhan
approved these changes
Sep 5, 2024
|
📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
chrisdent-de
pushed a commit
to chrisdent-de/PowerShell
that referenced
this pull request
Sep 12, 2024
* Set up CI with Start Right * remove deadcode and add copyright notice * Update .pipelines/templates/compliance/apiscan.yml * Apply suggestions from code review * fix syntax
adityapatwardhan
pushed a commit
to adityapatwardhan/PowerShell
that referenced
this pull request
Sep 19, 2024
* Set up CI with Start Right * remove deadcode and add copyright notice * Update .pipelines/templates/compliance/apiscan.yml * Apply suggestions from code review * fix syntax
adityapatwardhan
added a commit
that referenced
this pull request
Sep 20, 2024
adityapatwardhan
pushed a commit
to adityapatwardhan/PowerShell
that referenced
this pull request
Oct 15, 2024
* Set up CI with Start Right * remove deadcode and add copyright notice * Update .pipelines/templates/compliance/apiscan.yml * Apply suggestions from code review * fix syntax
adityapatwardhan
added a commit
that referenced
this pull request
Oct 15, 2024
This was referenced Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This pull request introduces new pipeline configurations for API scanning and notice file generation. The changes include the addition of new YAML files to define the pipeline structure and the necessary steps for these processes. Below are the most important changes:
New Pipeline Configuration for API Scanning
.pipelines/apiscan-gen-notice.yml: Added a new pipeline configuration file to define variables, resources, and stages for API scanning and notice file generation..pipelines/templates/compliance/apiscan.yml: Added a template for the API scanning job, including steps for checking out the repository, installing necessary tools, and running the API scan.New Pipeline Configuration for Notice File Generation
.pipelines/templates/compliance/generateNotice.yml: Added a template for generating a notice file, including steps for component detection, verifying license data, and uploading the notice file to Azure Blob Storage.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.- [ ] Issue filed:
(which runs in a different PS Host).