zaproxy-plugin weirdness and request

[JordanGS]

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, 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)
ZAProxy Plugin

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.

I have updated the Wiki and the README 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. :)

[Daniel Beck]

> On 16.11.2016, at 01:59, JordanGS <develop...@gmail.com> wrote:
>
> 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."
>

We don't really use long descriptions in Jira. If you look to all other plugins, they have very short descriptions as well. Not sure whether layout of some overview/list page would break, so I'd rather not do this.

[JordanGS]

Okay let's make the description just "zap-plugin"