Process for deleting plugins?

[R. Tyler Croy]

Do we have a process in place for deleting or otherwise archiving plugins? I
was pointed to the Gitorious plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Gitorious+Plugin) which is an
integration for a service which has been dead for a long time now.


As part of Hacksgiving
(https://wiki.jenkins-ci.org/display/JENKINS/Hacksgiving+2015) I'd like to
clean this up and remove it from the update center, etc, but I'm not sure we
have a defined process for this yet do we?


Cheers
- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Slide]

+1 it would definitely be nice to clean some up.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20151113182639.GN23766%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.

[Manuel Jesús Recena Soto]

+1 absolutely.

> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdDXQKQoO56Wdo5yv3Lz-D_3T2pg2WTEOVUKX-G_hg3Jw%40mail.gmail.com.

>
> For more options, visit https://groups.google.com/d/optout.

--
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

[Martin Weber]

Am Freitag, 13. November 2015, 10:26:39 schrieb R. Tyler Croy:
> Do we have a process in place for deleting or otherwise archiving plugins? I
> was pointed to the Gitorious plugin
> (https://wiki.jenkins-ci.org/display/JENKINS/Gitorious+Plugin) which is an
> integration for a service which has been dead for a long time now.

shining-panda is also dead.

>
>
> As part of Hacksgiving
> (https://wiki.jenkins-ci.org/display/JENKINS/Hacksgiving+2015) I'd like to
> clean this up and remove it from the update center, etc, but I'm not sure we
> have a defined process for this yet do we?

Moving them to a 'retired' repo might be a way.

Martin

--
Cd wrttn wtht vwls s mch trsr.

[Baptiste Mathus]

Well, there's already a std way to hide plugins: https://github.com/jenkinsci/backend-update-center2/blob/master/src/main/resources/artifact-ignores.properties

But to my knowledge, there's no process per-se. You mean something complete with moving sources somewhere else + hiding it with the above?

--
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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2594504.q7QLjpJ1dr%40linux.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Daniel Beck]

On 13.11.2015, at 21:12, Martin Weber <fifteen...@gmail.com> wrote:

> shining-panda is also dead.

Isn't their plugin just a better Python Plugin now?

[Martin Weber]

Oops. Look*s like it is now.
In 2013, I registered at shining-pande dot dontremember for a free service
that would build my FOSS project. It then was number 297 on their list of
projects to get approval. Six months later they announced to shut down their
build service.

Sorry for the confusion, according to [1], the plugin is not dead.

Martin

[1] http://shiningpanda.com/shiningpanda-plugin-022.html

[R. Tyler Croy]

(replies inline)

On Fri, 13 Nov 2015, R. Tyler Croy wrote:

> Do we have a process in place for deleting or otherwise archiving plugins? I
> was pointed to the Gitorious plugin
> (https://wiki.jenkins-ci.org/display/JENKINS/Gitorious+Plugin) which is an
> integration for a service which has been dead for a long time now.

I've started to put a draft together of a Plugin deletion process on this wiki
page:
<https://wiki.jenkins-ci.org/display/JENKINS/Deleting+a+Plugin>

Please take a look at it when you get a chance

[evernat]

Hi Tyler,

When there is a wiki page, it seems enough to put a "plugin-deprecated" label and a deprecated notice in the wiki page like the Nabaztag plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Nabaztag+Plugin
and others:
https://wiki.jenkins-ci.org/label/JENKINS/plugin-deprecated
You could do that for the gitorious plugin.

When there is no wiki page, for example when the plugin was just renamed, it is needed to add it to:
https://github.com/jenkinsci/backend-update-center2/blob/master/src/main/resources/artifact-ignores.properties

bye,
Emeric

[Kanstantsin Shautsou]

This plugin still has 240 active installations, why should you remove it?

[Oleg Nenashev]

I think that we should not remove plugins from UC, because there can be OLD Jenkins versions using OLD service versions. We cannot track it. Printing warnings is a right option IMO.
At least it increases the chance that somebody takes ownership of them.

When there is a wiki page, it seems enough to put a "plugin-deprecated" label and a deprecated notice in the wiki page like the Nabaztag plugin

+1

When there is no wiki page, for example when the plugin was just renamed, it is needed to add it to...

In such case I would create a Wiki page stub just for consistency purposes.
In such case it may also have adopt-a-plugin label

 

суббота, 14 ноября 2015 г., 14:33:01 UTC+3 пользователь evernat написал:

[Christopher Orr]

On 14/11/15 16:45, Oleg Nenashev wrote:
> I think that we should not remove plugins from UC, because there can be
> OLD Jenkins versions using OLD service versions. We cannot track it.
> Printing warnings is a right option IMO.
> At least it increases the chance that somebody takes ownership of them.

I think if someone's using an old plugin version and has never upgraded,
removing it from the UC won't hurt them.

The original question was about removing plugins that no longer have any
use, so I think it's reasonable to remove plugins from the UC for
services that no longer exist, e.g. the Nabaztag plugin, the Gitorious
plugin, or the Hudson Google Desktop Gadget plugin.

What I did do, for example, on the Nabaztag page, was to add a link to
the archived plugin releases, in case somebody (for whatever weird
reason) needs to download a version in future.

>> When there is a wiki page, it seems enough to put a
>> "plugin-deprecated" label and a deprecated notice in the wiki page
>> like the Nabaztag plugin
>
> +1

Adding "plugin-deprecated" to a wiki page prevents a plugin from
appearing in the UC, so your +1 here conflicts with your statement above
;) :D

Regards,
Chris

[evernat]

Hi,

I have added a wiki page to list the deprecated plugins.
And in order to display them only in this page and not in the page of the available plugins among others, I have added to the process of plugin deprecation: "remove labels other than plugin-deprecated from the wiki page of the plugin". I have already applied that to all deprecated plugins.
Hopefully, it makes the list of available plugins a bit more readable.

bye,
Emeric

Le samedi 14 novembre 2015 01:41:44 UTC+1, R Tyler Croy a écrit :