Stopping plugin hosting

[Petr Chudanič]

Hi Everyone

I have a Jenkins plugin that is hosted in Jenkins Update Centre.

As we are considering to release new plugin with different name that would contain current plugin's functionality plus more we would like to remove it from Update Center.

I'd like to know what is the correct process to take it down (hide/remove it from update center) - if it is possible at all.

Thanks for any suggestions.

Petr Chudanic

[Daniel Beck]

> On 20. Feb 2018, at 12:30, Petr Chudanič <chud...@gmail.com> wrote:
>
> I have a Jenkins plugin that is hosted in Jenkins Update Centre.
>
> As we are considering to release new plugin with different name that would contain current plugin's functionality plus more we would like to remove it from Update Center.
>
> I'd like to know what is the correct process to take it down (hide/remove it from update center) - if it is possible at all.

https://github.com/jenkins-infra/backend-update-center2#removing-plugins-from-distribution

But note that existing users will not receive updates, and cannot automatically "upgrade" to the new plugin. And having both installed with probably result in a broken experience.

[Antonio Muñiz]

> But note that existing users will not receive updates, and cannot automatically "upgrade" to the new plugin

Making a tombstone release makes more difficult to get both plugins installed.

1. Release the new plugin

2. Remove all the code from the old plugin

3. Leave a minimal pom.xml, with a single dependency to the new plugin

4. Release the old plugin

So users will get an update for old-plugin which is basically removing it and automatically installing the new one.

Still, users could install the new plugin directly and get in troubles. I guess this can be solved by documentation and release notes in both plugins.

--
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-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6C204817-79D8-444F-BE77-7CAEEF35C205%40beckweb.net.

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

--

Antonio Muñiz

Software Engineer
CloudBees, Inc.

[Jesse Glick]

On Tue, Feb 20, 2018 at 8:00 AM, Antonio Muñiz <amu...@cloudbees.com> wrote:
> Still, users could install the new plugin directly and get in troubles. I
> guess this can be solved by documentation and release notes in both plugins.

Or: https://issues.jenkins-ci.org/browse/JENKINS-49651

[Petr Chudanič]

Thanks, seems interesting, we may end up going for this solution

Dne úterý 20. února 2018 14:00:39 UTC+1 Antonio Muñiz napsal(a):

> But note that existing users will not receive updates, and cannot automatically "upgrade" to the new plugin

Making a tombstone release makes more difficult to get both plugins installed.

1. Release the new plugin

2. Remove all the code from the old plugin

3. Leave a minimal pom.xml, with a single dependency to the new plugin

4. Release the old plugin

So users will get an update for old-plugin which is basically removing it and automatically installing the new one.

Still, users could install the new plugin directly and get in troubles. I guess this can be solved by documentation and release notes in both plugins.

On 20 February 2018 at 13:46, Daniel Beck <m...@beckweb.net> wrote:

> On 20. Feb 2018, at 12:30, Petr Chudanič <chud...@gmail.com> wrote:
>
> I have a Jenkins plugin that is hosted in Jenkins Update Centre.
>
> As we are considering to release new plugin with different name that would contain current plugin's functionality plus more we would like to remove it from Update Center.
>
> I'd like to know what is the correct process to take it down (hide/remove it from update center) - if it is possible at all.

https://github.com/jenkins-infra/backend-update-center2#removing-plugins-from-distribution

But note that existing users will not receive updates, and cannot automatically "upgrade" to the new plugin. And having both installed with probably result in a broken experience.

--
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/6C204817-79D8-444F-BE77-7CAEEF35C205%40beckweb.net.

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