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.

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

Failed to initialize the RetireJS repo #1394

Closed
ghost opened this issue Jul 23, 2018 · 10 comments
Closed

Failed to initialize the RetireJS repo #1394

ghost opened this issue Jul 23, 2018 · 10 comments
Labels

Comments

@ghost
Copy link

ghost commented Jul 23, 2018

When the data directory is in a different path than the temporary directory, the retirejs analyzer fails with "Failed to initialize the RetireJS repo" exception. See https://gist.github.com/bcartolo/d737e07be45a9eb3bfaa4bfcc6cdbdd0

@jeremylong jeremylong added the bug label Jul 24, 2018
jeremylong added a commit that referenced this issue Jul 24, 2018
@waded
Copy link

waded commented Jul 25, 2018

One possible workaround is to disable the RetireJS analyzer for now, e.g. in the Maven plugin config:

<configuration>
    <retireJsAnalyzerEnabled>false</retireJsAnalyzerEnabled>
</configuration>

@ghost
Copy link
Author

ghost commented Jul 25, 2018

Another one is to change the location of the data directory to the same drive of the temporary directory (Or the other way around).

@stevespringett
Copy link
Collaborator

I also believe we need to remove the check to see if the analyzer is enabled or not prior to downloading. This behavior is inconsistent with other analyzers (like the NVD) which doesn't have this check. I had to 'enable' the retireJs analyzer in order to perform an updateOnly. Without the analyzer enabled, I received the same "Failed to initialize the RetireJS repo" exception.

@jortkoopmans
Copy link

jortkoopmans commented Jul 26, 2018

Also been hitting this problem, breaking my builds. I've rolled back to 3.2.1.

EDIT: Clarifying my setup: running Jenkins master in a docker container, on a CentOS7 host. Various build nodes around it, I've seen this problem occur on linux (CentOS7) based builds using the DependencyCheck.

@stevespringett
Copy link
Collaborator

@javixeneize
Copy link

Hi. Is a Jenkins plugin version going to be released for this as well?

Thanks

@stevespringett
Copy link
Collaborator

@javixeneize jenkins plugin 3.3.1 is already released and has this functionality.

@javixeneize
Copy link

Hi. It is still failing for me on that version

[DependencyCheck] OWASP Dependency-Check Plugin v3.3.1

[DependencyCheck] Analyzing Dependencies
[DependencyCheck] One or more exceptions were thrown while executing Dependency-Check
[DependencyCheck] Exception Caught: org.owasp.dependencycheck.exception.InitializationException
[DependencyCheck] Cause: 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

@jeremylong
Copy link
Owner

You would need to provide the debug log - and I might recommend opening a new issue.

@lock
Copy link

lock bot commented Sep 27, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Sep 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants