-
Improvement
-
Resolution: Won't Do
-
Minor
-
None
Currently we are missing Jenkins Pipeline options to enable or disable the specific analyzers, something like:
jarAnalyzerEnabled: true nodeJsAnalyzerEnabled: true nspAnalyzerEnabled: true composerLockAnalyzerEnabled: true pythonDistributionAnalyzerEnabled: true pythonPackageAnalyzerEnabled: true rubyBundlerAuditAnalyzerEnabled: true rubyGemAnalyzerEnabled: true cocoaPodsAnalyzerEnabled: true swiftPackageManagerAnalyzerEnabled: true archiveAnalyzerEnabled: true assemblyAnalyzerEnabled: true centralAnalyzerEnabled: true nuspecAnalyzerEnabled: true nexusAnalyzerEnabled :false autoconfAnalyzerEnabled: true cmakeAnalyzerEnabled: true opensslAnalyzerEnabled: true
The plugin always inherits the global configuration (defaults to everything enabled).
Why do we need this?
- This is an issue for Jenkins instances that are managed with Ansible/Puppet, because it's not easy to change the global configuration. Also see
JENKINS-46746 - When running many projects on the same instance; different projects might need different analytic scopes.