[Feature Request] Allow to share the scanner config file between CI/CD processes and developer environments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by tracing how code-analyzer.yml is consumed by the command-line scanner and whether the Visual Studio Code extension reads it, then inspect how java_classpath_entries and PMD rule-set selection are resolved. Done means the same scanner configuration can use environment-specific PMD paths and rule sets in CI/CD, command-line use, and Visual Studio Code.
Written by the indexing model from the issue text.
Description
Need/Problem Description
As a developer, I would like to use the same scanner configuration which is used when running CI/CD processes (including same custom PMD rules) while my PMD jars containing classes required by the custom PMD rules are located in other folders than for CI/CD processes - both when using the command line as well as in Visual Studio Code.
Describe your Desired Solution
An environment variable could be used inside the PMD classpath in code-analyzer.yml:
java_classpath_entries:
- %CUSTOM_PMD%/pmd-jars/pmd-customjar.jar
Or;
java_classpath_entries:
- %CUSTOM_PMD_JARS%
A second variable could contain the PMD rule sets to execute.
The environment variable could be set to correct values in CI/CD and for each developer machine.
While I believe that the Visual Studio Code extension does not consider the scanner configuration file (code-analyzer.yml), if that is implemented, it could consider that environment variable as well.
Alternatives Considered
No response
Additional Context (Screenshots, Files, etc)
No response
Workaround
No response
Urgency
Low
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
forcedotcom/code-analyzer#2100 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day