Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41069

Speed difference between UI and Jenkins plugin

      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,

          [JENKINS-41069] Speed difference between UI and Jenkins plugin

          Goran Sarenkapa added a comment - - edited

          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.

          Goran Sarenkapa added a comment - - edited 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.

          Now under zap-plugin component.

          Ricardo Pereira added a comment - Now under zap-plugin component.

          Hi jammasterj89, I haven't been able to replicate this issue. Can you try to update to the latest version and re-run?

          Google Group: https://groups.google.com/forum/#!topic/zaproxy-jenkins/PJBysyheHdw

          Goran Sarenkapa added a comment - Hi jammasterj89 , I haven't been able to replicate this issue. Can you try to update to the latest version and re-run? Google Group: https://groups.google.com/forum/#!topic/zaproxy-jenkins/PJBysyheHdw

          Goran Sarenkapa added a comment - - edited

          CLOSED: False positive

          Description: No issue with the API or plugin, user reconfiguration of the logged in indicator caused the issue.

          Goran Sarenkapa added a comment - - edited CLOSED : False positive Description: No issue with the API or plugin, user reconfiguration of the logged in indicator caused the issue.

            jordangs Goran Sarenkapa
            jammasterj89 javaers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: