Open jiri-bocan opened 1 year ago
See https://github.com/jeremylong/DependencyCheck/issues/5154 and the ticket we opened with the OSS Index: https://github.com/sonatype/ossindex-public/issues/42
Thanks, @jeremylong. But that ossindex issue seems unrelated to the exit code 14, right? Plus, as mentioned, we have not seen this in versions before 8.1.2.
Pretty much any non-fatal error will return an exit code of 14:
Running OWASP scan in the DevOps pipeline failed with the same error if the project targetFramweok is net standard. However, does setting the target to 452 or 462 work fine?
The team is using .NET Core 6. But will keep this in mind. Thanks, @Was85.
I just encountered this morning as well, our devops pipeline failed for all projects.
In the report, they all show this error: java.lang.NullPointerException exception: org.owasp.dependencycheck.analyzer.exception.AnalysisException: java.lang.NullPointerException org.owasp.dependencycheck.analyzer.MSBuildProjectAnalyzer.analyzeDependency(MSBuildProjectAnalyzer.java:210) org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131) org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88) org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) $enc.html($ex.getMessage())
@lachlann562 this is a different error - which will be fixed in 8.2.1.
What about this issue? It closed in latest versions?
Describe the bug After updating to the latest version 8.1.2, some of the repo scans started failing with exit code 14.
Version of dependency-check used Installed prerequisite: .NET SDK 6.x (for Linux) via Azure pipeline. OWASP 8.1.2 downloaded and installed in a separate task. A scan task is as follows (OWASPDependencyCheck@0 deprecated, using dependency-check-build-task@6 instead; since the localInstallPath is specified, nothing is installed there):
Log file
Expected behavior Likely to throw a warning (or error) but proceed without failing the entire build.
Additional context Versions between 7.0.0. and 8.1.0 (including) have not reported the above-mentioned issue for a given repository.