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

Getting Timeout on running FOD command #79

Open
ronaldfrancisabas opened this issue Sep 2, 2024 · 1 comment
Open

Getting Timeout on running FOD command #79

ronaldfrancisabas opened this issue Sep 2, 2024 · 1 comment
Labels
question Further information is requested

Comments

@ronaldfrancisabas
Copy link

Question

We would like to check why the following command takes time to complete in which resulting to timeout
FortifyVulnerabilityExporter FoDToGitLabSAST --fod.baseUrl=$FOD_URL --fod.tenant="$FOD_TENANT" --fod.userName="$FOD_USERNAME" --fod.password="$FOD_PAT" --fod.release.id=$FOD_RELEASE

@ronaldfrancisabas ronaldfrancisabas added the question Further information is requested label Sep 2, 2024
@rsenden
Copy link
Contributor

rsenden commented Sep 2, 2024

Hi, can you provide some more details? Does the command itself generate a timeout error, is it your pipeline that's timing out because the command is taking too long, ...? How many vulnerabilities do you have in your FoD release, and how long does it take until timeout? Any logs/snippets you can share?

The command needs to load all vulnerability data from FoD, which may take quite some time, especially if you have a large number of vulnerabilities, and FoD rate limiting may further reduce performance.

Although it probably won't make much difference regarding performance, have you checked out the same functionality that's now available in fcli? fcli fod action run gitlab-sast-report
As mentioned in the deprecation notice, we plan on deprecating FortifyVulnerabilityExporter and ask customers to move to fcli.

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

No branches or pull requests

2 participants