CSEDevOps icon indicating copy to clipboard operation
CSEDevOps copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

##[error]ENOENT: no such file or directory, open '/home/vsts/work/1/s/owaspzap/report.json'

Open XSniper001 opened this issue 2 years ago • 7 comments

Please any help !! 1 2 !

XSniper001 avatar Apr 16 '22 21:04 XSniper001

any update on it please?

aruntestgit avatar Aug 17 '22 13:08 aruntestgit

I am getting the same error. Seems to be specific to Azure Pipelines as I don't get any errors when attempting to run this task in my Release Definition.

oZakari avatar Aug 25 '22 19:08 oZakari

@oZakari Is it possible to have your yaml implementation? Because I have the same error in release pipeline. Thx!

QuentinBeeckmans avatar Dec 21 '22 14:12 QuentinBeeckmans

@QuentinBeeckmans This is the YAML for the task I am using in my classic release definition.

steps:
 - task: CSE-DevOps.zap-scanner.custom-build-release-task.owaspzap@1
  displayName: 'ZAP Scanner'
  inputs:
    scantype: targetedScan
    url: 'https://tester.azurewebsites.net'
    port: 443`

oZakari avatar Dec 21 '22 15:12 oZakari

@oZakari It's really crazy. I have the same task: steps:

  • task: CSE-DevOps.zap-scanner.custom-build-release-task.owaspzap@1 displayName: 'ZAP Scanner' inputs: threshold: 500 scantype: targetedScan url: 'https://appmonitoringstoragemanager.azurewebsites.net' port: 443

and it doesn't work.

QuentinBeeckmans avatar Dec 23 '22 20:12 QuentinBeeckmans

@QuentinBeeckmans I just tested using a new app service without any code deployments and it still works. I am using the Microsoft Hosted ubuntu-latest agent pool if you want to check that.

oZakari avatar Jan 05 '23 02:01 oZakari

@oZakari thanks for your help but I have finally use in an command line the Docker image directly and It work too

QuentinBeeckmans avatar Jan 05 '23 09:01 QuentinBeeckmans