-
Notifications
You must be signed in to change notification settings - Fork 607
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
Resolve/Suppress remaining Cloud Manager Code Scanning Blocker/Criticals as of 2022-01-18 #2772
Comments
@adamcin you want help w/ any of these? and/or want me to assign to you? Once these are finished we can cut a release and clear out the CM speedbump. |
@davidjgonzalez Yep, I'm running through them in our sandbox. |
@davidjgonzalez I have a passing Code Quality check with 2 commits on top of PR #2771 . I'm afraid to push them to the PR branch because of the inevitably huge coverage requirement :) |
The coverage requirement can be adjusted. This is not set in stone. @adamcin What metric value do you consider reasonable in .codecov.yml |
… affecting security score
…n code quality pipeline
I'll push the commits and just wait to see what happens to the PR patch coverage score. |
@davidjgonzalez @kwin @joerghoh It looks like no coverage requirement adjustment is necessary. All checks in #2771 passed with the added commits, and the branch passes a CM Code Quality pipeline with no overrides. |
Required Information
Expected Behavior
Customers deploying ACS AEM Commons should not have override Blocker/Critical issues related to as-is code.
Actual Behavior
After merge of #2771 , some remaining Blocker/Critical Java issues are still flagged in CM:
Steps to Reproduce
Push affected tip to a CM repo and trigger a Code Quality pipeline.
The text was updated successfully, but these errors were encountered: