You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My OWASP dependency reports stopped listing vulernabilies, when I know there are many. I recently had to do a --purge which might be when they broke. What could be wrong?
I will add that i have multiple projects using the same build agent folder. Each project use it's own setting report directory. Each build is using the same folder for downloading dependecy-check.
E.g. The folder/command is the same for each project's build
/home/azdevops/myagent-04/_work/_tasks/dependency-check-build-task_47ea1f4a-57ba-414a-b12e-c44f42765e72/6.2.3/dependency-check/bin/dependency-check.sh
Is something cached in the dependency-check folder that is causing the dependecy report to break?
Do I have to use a different build agent for each project ?
You provide 0 output of dependencycheck. So you need to make your task capture the SysOut/SysErr of the shell command (dependencycheck.sh invocation) if you want this project to give you any advice.
You need to check with the authors and documentation of the azure dependency-check-build-task how to obtain the output of the dependencycheck.sh that they invoke in the task.
My OWASP dependency reports stopped listing vulernabilies, when I know there are many. I recently had to do a --purge which might be when they broke. What could be wrong?
Yml
Build Info:
Report:
The text was updated successfully, but these errors were encountered: