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

Exports using GitHub or GitLab configuration files fail on Windows #7

Closed
rsenden opened this issue Mar 9, 2021 · 1 comment
Closed

Comments

@rsenden
Copy link
Contributor

rsenden commented Mar 9, 2021

Running FortifyVulnerabilityExporter on Windows results in an error if any of the following environment variables is set to an absolute path with drive letter:

  • EXPORT_DIR (all configuration files that refer to export.dir)
  • GITHUB_WORKSPACE (all GitHub-related configuration files)
  • CI_PROJECT_DIR (all GitLab-related configuration files)

The error doesn't occur in the following cases:

  • When using an absolute path without drive letter, i.e. \Temp\SomeDir
  • If the output file already exists (the error does occur though if the output directory exists but the file does not exist)

Errors look something like the below:

    Failed to bind properties under 'json.gitlab.dast.output.file' to java.io.File:

    Property: json.gitlab.dast.output.file
    Value: ${export.dir}/gl-fortify-dast.json
    Origin: URL [file:config/FoDToGitLab.yml] - 35:11
    Reason: failed to convert java.lang.String to java.io.File
@rsenden
Copy link
Contributor Author

rsenden commented Mar 10, 2021

Root cause is described here: spring-projects/spring-boot#25566

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant