-
Bug
-
Resolution: Done
-
Minor
Hi there,
I am noticing a speed difference between the Jenkins plugin and the ZAP UI.
When I am running a spider then an active scan using the Jenkins plugin, it takes 1.5 hours to complete a spider, and 100+ hours to complete an active scan (medium policy).
However, if I run the same spider and active scan through the ZAP UI running the same ZAP.sh, the spider takes seconds and the active scan completes within an hour, both are using the same session file.
Version info:
Jenkins 2.19.4
ZAP Plugin 1.0.5
ZAP weekly version D-2017-01-09
Ubuntu 16.04 (virtual machine)
Session.data file ~100mb for local web application on same network
Thanks in advance,
Wrong component and reporting area. This is the zaproxy-plugin which is deprecated.
The official plugin is here and information on where to report issues can be found under Issue Tracking Heading. The proper component being zap-plugin
If it wasn't for the google group area i would not have even checked here. This zaproxy-plugin component is no longer maintained or observed by anyone and is not related to the official zap proxy plugin.