search

dependency-check / azuredevops

Dependency Check Azure DevOps Extension
Apache License 2.0
44 stars 26 forks source link

6.2.1 Fails: #[error]Not found Dependency Check installer: D:\a\1\s\dependency-check #161

Closed Wes-Love closed 2 months ago

Wes-Love commented 2 months ago

Describe the bug 6.2.1 Fails with the error : #[error]Not found Dependency Check installer: D:\a\1\s\dependency-check

To Reproduce Steps to reproduce the behavior:

  1. Run a build including dependancy checker ( I am using the Azure Build Agent)

Expected behavior It does not fail

Logs Full Log:

Starting: Dependency Check

Task : OWASP Dependency Check Description : Dependency Check is a Software Composition Analysis (SCA) tool that attempts to detect publicly disclosed vulnerabilities contained within a project's dependencies. Version : 6.2.1 Author : Dependency Check Help : More Information

Starting Dependency Check... Setting report directory to D:\a\1\TestResults\dependency-check Creating report directory at D:\a\1\TestResults\dependency-check Not found Dependency Check installer: D:\a\1\s\dependency-check

[error]Not found Dependency Check installer: D:\a\1\s\dependency-check

[error]Unhandled error condition detected.

Ending Dependency Check... Finishing: Dependency Check

Additional context this was working 1 hr ago with 6.2.0

schauers commented 2 months ago

We Encounter the Same Error

AFAde commented 2 months ago

Experiencing the same problem too

jepp-igus commented 2 months ago

Same problem on linux based machines image

Rolled back to previous version.

ajeckmans commented 2 months ago

Same here :)

DmitryKozlovVentionteams commented 2 months ago

Same issue... We'd highly appreciate if it can be fixed asap...

jepp-igus commented 2 months ago

Workaround:

Changing the task version from

- task: dependency-check-build-task@6

to 

- task: dependency-check-build-task@6.2.0

will do the trick until a hotfix has been released...

ajeckmans commented 2 months ago

6.2.0 also has an open issue (#158) so I went to 6.1.3. This is not possible for non-yaml pipelines btw.

DmitryKozlovVentionteams commented 2 months ago

6.2.0 also has an open issue (#158) so I went to 6.1.3. This is not possible for non-yaml pipelines btw.

Thanks @ajeckmans , this workaround works for us (we use the only yml-pipelines)

pippolino commented 2 months ago

The version 6.2.3 has been released with a fix.

Wes-Love commented 2 months ago

6.2.3 fixed it for me. Thanks