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

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

Open
XSniper001 opened this issue Apr 16, 2022 · 7 comments
Labels

Comments

@XSniper001
Copy link

Please any help !!
1
2
!

@aruntestgit
Copy link

any update on it please?

@oZakari
Copy link

oZakari commented Aug 25, 2022

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.

@QuentinBeeckmans
Copy link

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

@oZakari
Copy link

oZakari commented Dec 21, 2022

@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`

@QuentinBeeckmans
Copy link

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

and it doesn't work.

@oZakari
Copy link

oZakari commented Jan 5, 2023

@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.

@QuentinBeeckmans
Copy link

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

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

No branches or pull requests

5 participants