Plugin IDs (or plugin IDs + version number) can be blacklisted in the update center. https://github.com/orrc/backend-update-center2/blob/master/src/main/resources/artifact-ignores.properties
Not sure whether this particular plugin warrants that step though -- any further opinions? Would be great if the plugin developers could chime in as well on why they decided to go ahead and release rather than address the concerns expressed in this thread (and which are well documented, e.g. on https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin). On 10.10.2015, at 23:58, Victor Martinez <[email protected]> wrote: > That's bad!! Is there any wiki of how to proceed in case a new plugin has > been released without being part of the standard release? I didn't know > people could release directly without agreeing. Any chance to somehow > rollback that plugin from the update center and talk again whether it should > be part of the claim plugin or an independent plugin as now? > > Cheers > > -- > 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/c1b620c1-8be8-44a3-af6f-c2c79c654176%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/6DCC6B70-1E12-4DD7-8D52-015F887277A4%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
