1. At the request of jenkins admin's, i have reverted all changes made to the jenkins zaproxy-plugin. Updated the readme to inform users that it is discontinued.
If you look at cloudbees <https://jenkins.ci.cloudbees.com/job/plugins/job/zaproxy-plugin/>, the build's seem to be failing. It is failing because it cannot resolve dependencies, this is expected. Module Builds Official OWASP Zed Attack Proxy Jenkins Plugin (didn’t run) [image: Failed] <https://jenkins.ci.cloudbees.com/job/plugins/job/zaproxy-plugin/184/fr.novia$zaproxy/> ZAProxy Plugin <https://jenkins.ci.cloudbees.com/job/plugins/job/zaproxy-plugin/184/fr.novia$zaproxy/> I am unsure why it saying "Official OWASP Zed Attack Proxy Jenkins Plugin" because that label should be removed?? --- 2. As discussed in IRC, can we discontinue distribution of the current plugin but still allow existing users of the plugin to use the current version while we expect migration to zap-plugin <https://github.com/jenkinsci/zap-plugin>. I have updated the Wiki <https://wiki.jenkins-ci.org/display/JENKINS/ZAProxy+Plugin>and the README <https://github.com/jenkinsci/zaproxy-plugin> in accordance with deprecating a plugin. 3. Can someone with voice please change the description under https://issues.jenkins-ci.org/ for the component zap-plugin jenkins-admin: set description of zap-plugin to "The Official OWASP ZAP Jenkins Plugin extends the functionality of the ZAP security tool into a CI Environment." --- Thank you. :) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d796c010-15ec-4b1b-b0f8-cad9bb5cc972%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
