Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sonar scan running on compiled target directory #4

Open
paulbourelly999 opened this issue Apr 15, 2024 · 0 comments
Open

Sonar scan running on compiled target directory #4

paulbourelly999 opened this issue Apr 15, 2024 · 0 comments
Labels
anomaly bug Something isn't working

Comments

@paulbourelly999
Copy link
Contributor

paulbourelly999 commented Apr 15, 2024 •
edited
Loading

Summary

Remove all target directories from sonar static analysis. Theses contain built/compiled files from source and do not need to be exposed to static analysis. They create duplicate reports of code smells

Commit

ddfe66b

Expected Behavior

Static analysis only happens on source code

Actual Behavior

Static analysis happens on both source code and compiled code. Code smells and security issues are reported twice, once in source code and once in compiled code.

Steps to Reproduce the Actual Behavior

  1. Run static analysis
  2. Look for code smells in target/ directories.

Related Work

No response
@paulbourelly999 paulbourelly999 added anomaly bug Something isn't working labels Apr 15, 2024
@paulbourelly999 paulbourelly999 changed the title Current repo has committed build files Sonar scan running on compiled target directory Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
anomaly bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paulbourelly999