-
Notifications
You must be signed in to change notification settings - Fork 2
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: added NuGet and npm packages licenses checks on PR build validation #172347 #26
base: main
Are you sure you want to change the base?
feat: added NuGet and npm packages licenses checks on PR build validation #172347 #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if these 3 files should be in the build folder? Maybe like the dependency check steps they could live in /src/security/license-checks/
?
Not sure they are strictly security though 😆 happy to see what anyone else thinks.
inputs: | ||
scriptType: inlineScript | ||
inlineScript: | | ||
$licenses = @("MIT","Apache-2.0","BSD-3-Clause","Apache-2.0 OR MPL-2.0","MS-EULA","X11","Unlicense","0BSD","BSD-2-Clause") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There definitely doesn't need to be any project specific overrides of any of these configs? Or at least not in v1?
@@ -69,6 +69,10 @@ jobs: | |||
--configuration Release | |||
--no-restore | |||
|
|||
- template: /src/build/common/steps/license-checks.steps.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need to happen after the build? It can't go up at the top with the dependency check? Feels a bit random here between Build and Test
steps: | ||
- script: | | ||
dotnet new tool-manifest | ||
dotnet tool install dotnet-project-licenses |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the one being installed? It says it is abandoned
Code ready for review
YAML pipeline syntax validated
README or other documentation updated
Added/updated logging
Pipeline triggers verified
Secrets and variables managed
Dependency licenses
Pipeline steps documented
Security vulnerabilities checked