-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
RetireJS failing in Jenkins plugin #1467
Comments
Can you increase the logging on Jenkins and provide a more complete log so we can try and track down what is going on? |
Hi. I have increased log level to the maximum and still no extra information. The error is the same i was having in local when using the previous version if i didnt disable the retireJS repo, if it helps |
Same problem here in a Jenkins slave:
|
Same issue (and logs) with the 3.3.1 version of the plugin. With the version 3.2.1 works fine. |
Please enable Jenkins debug logging for 'org.owasp' and attach the resulting log containing the errors. |
I believe I have the same issue with the 3.3.4 version of the plugin. Here is the output plus I added org.owasp logs (First time so hopefully I got what you suggested on Sep 6). [DependencyCheck] Analyzing Dependencies |
same issue here |
We still need a full debug log from someone experiencing this issue. What has been provided is the end of the log; there should be a section near the start of the dependency-check run where the NVD data is initialized - this is also where the RetireJS data is downloaded and cached locally. Please enable Jenkins debug logging for 'org.owasp' and attach the resulting log containing the full output of dependency-check. |
@jeremylong here you go:
|
Looks like a connectivity issue instead of a DependencyCheck issue because of: [DependencyCheck] Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target |
Correct - the RetireJS Analyzer does download the RetireJS repository: https://raw.githubusercontent.com/Retirejs/retire.js/master/repository/jsrepository.json If you are mirroring the NVD you should probably mirror the Retire JS repository. However, we just added the configuration options to allow using a mirror. The options will be included in 5.0.0 (or possibly 5.0.0-m3 - we are still deciding if we are going to do one more milestone release before the final release of 5.0.0). |
This is related to issue #1394
I am using the latest DC plugin for Jenkins (3.3.1) and the tool is still failing when i have initialised RetireJS plugin. Note that this is happening when executing this in a Jenkins slave
Looks like the issue is that it tries to access to a file that doesnt exist (i dont know if it needs to be initialised in advance) If it helps, i am running it against a java application (.jar) so there is no reason to trigger the retirejs analyser
Here is the log:
[DependencyCheck] Analyzing Dependencies
[DependencyCheck] One or more exceptions were thrown while executing Dependency-Check
[DependencyCheck] Exception Caught: org.owasp.dependencycheck.exception.InitializationException
[DependencyCheck] Cause: /tmp/jsrepository.json (No such file or directory)
[DependencyCheck] Message: Failed to initialize the RetireJS repo
[DependencyCheck] org.owasp.dependencycheck.exception.InitializationException: Failed to initialize the RetireJS repo
[DependencyCheck] at org.owasp.dependencycheck.analyzer.RetireJsAnalyzer.prepareFileTypeAnalyzer(RetireJsAnalyzer.java:178)
[DependencyCheck] at org.owasp.dependencycheck.analyzer.AbstractFileTypeAnalyzer.prepareAnalyzer(AbstractFileTypeAnalyzer.java:83)
[DependencyCheck] at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.prepare(AbstractAnalyzer.java:107)
[DependencyCheck] at org.owasp.dependencycheck.Engine.initializeAnalyzer(Engine.java:825)
[DependencyCheck] at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:662)
[DependencyCheck] at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.executeDependencyCheck(DependencyCheckExecutor.java:172)
[DependencyCheck] at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.call(DependencyCheckExecutor.java:103)
[DependencyCheck] at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.call(DependencyCheckExecutor.java:46)
[DependencyCheck] at hudson.remoting.UserRequest.perform(UserRequest.java:153)
[DependencyCheck] at hudson.remoting.UserRequest.perform(UserRequest.java:50)
[DependencyCheck] at hudson.remoting.Request$2.run(Request.java:336)
[DependencyCheck] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
[DependencyCheck] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[DependencyCheck] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[DependencyCheck] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[DependencyCheck] at hudson.remoting.Engine$1$1.run(Engine.java:94)
[DependencyCheck] at java.lang.Thread.run(Thread.java:745)
[DependencyCheck] Caused by: java.io.FileNotFoundException: /tmp/jsrepository.json (No such file or directory)
[DependencyCheck] at java.io.FileInputStream.open0(Native Method)
[DependencyCheck] at java.io.FileInputStream.open(FileInputStream.java:195)
[DependencyCheck] at java.io.FileInputStream.(FileInputStream.java:138)
[DependencyCheck] at org.owasp.dependencycheck.analyzer.RetireJsAnalyzer.prepareFileTypeAnalyzer(RetireJsAnalyzer.java:173)
[DependencyCheck] ... 16 more
[DependencyCheck]
The text was updated successfully, but these errors were encountered: