How to rename a Jenkins plugin?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

How to rename a Jenkins plugin?

Matt Murphy

I’m the maintainer for the the IBM Application Security on Cloud plugin.  The cloud service that this plugin interacts with is no longer owned by IBM, so I’d like to rename the plugin.  I don’t want to publish a new plugin with the new name because that would force users to reconfigure their jobs.

 

I tried searching for steps to accomplish this, but I haven’t found anything.  Is it possible to rename a plugin (including changing the groupId)?

 

Thanks for your help.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Tim Jacomb
Normally you would update the plugin name in the your pom.xml and do a release

This will update the display name but not the artifact ID, i.e. it will still show up in URLs like the plugin site

Other than that I  think you need to publish a new version that has an administrative monitor / log messages telling users to migrate to the new one

Thanks
Tim

On Wed, 9 Oct 2019 at 09:55, Matt Murphy <[hidden email]> wrote:

I’m the maintainer for the the IBM Application Security on Cloud plugin.  The cloud service that this plugin interacts with is no longer owned by IBM, so I’d like to rename the plugin.  I don’t want to publish a new plugin with the new name because that would force users to reconfigure their jobs.

 

I tried searching for steps to accomplish this, but I haven’t found anything.  Is it possible to rename a plugin (including changing the groupId)?

 

Thanks for your help.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidP2-CX0p1LzkRx-W11vc6X8771fpxbFaf7f%2B6RtsHZXA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Daniel Beck
In reply to this post by Matt Murphy


> On 8. Oct 2019, at 19:01, Matt Murphy <[hidden email]> wrote:
>
> I tried searching for steps to accomplish this, but I haven’t found anything.  Is it possible to rename a plugin (including changing the groupId)?

Group ID can be changed, just need an update of the permissions YAML file. Display name can be changed arbitrarily. Artifact ID is the difficult one. If you change that, it's considered a different plugin, so your users will need to migrate.

You might be able to make it easier by moving actual code over to the new plugin, adding a dependency to the new plugin from the (now gutted) old plugin, and then users *should* get the migration mostly for free. Add an admin monitor informing them that the old plugin can now be removed, and done.

This is not a particularly well-travelled path though, so there may be unexpected problems, and it might be easier to just live with the with the old artifact ID. Older components in the Pipeline plugins suite still have the ca. pre-2015 'workflow-' prefix.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7A62B449-8FA2-4114-B0A2-B119AE28C259%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Matt Murphy
Thanks.  Unfortunately, the artifactId contains "ibm", so I would like to change that, as well.  That's an interesting idea regarding having the new plugin depend on the old one.  I'll look into that.

On Wednesday, October 9, 2019 at 9:44:25 AM UTC-4, Daniel Beck wrote:


> On 8. Oct 2019, at 19:01, Matt Murphy <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="eaLA_GhwCwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">matthe...@...> wrote:
>
> I tried searching for steps to accomplish this, but I haven’t found anything.  Is it possible to rename a plugin (including changing the groupId)?

Group ID can be changed, just need an update of the permissions YAML file. Display name can be changed arbitrarily. Artifact ID is the difficult one. If you change that, it's considered a different plugin, so your users will need to migrate.

You might be able to make it easier by moving actual code over to the new plugin, adding a dependency to the new plugin from the (now gutted) old plugin, and then users *should* get the migration mostly for free. Add an admin monitor informing them that the old plugin can now be removed, and done.

This is not a particularly well-travelled path though, so there may be unexpected problems, and it might be easier to just live with the with the old artifact ID. Older components in the Pipeline plugins suite still have the ca. pre-2015 'workflow-' prefix.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/caabe870-71ce-4a6b-ada8-e8b9dc43703f%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Matt Murphy
In reply to this post by Tim Jacomb
Thanks for your response.  I'll look into using the admin monitor as a way of alerting users about the new plugin.


On Wednesday, October 9, 2019 at 9:13:41 AM UTC-4, Tim Jacomb wrote:
Normally you would update the plugin name in the your pom.xml and do a release
<a href="https://github.com/jenkinsci/ibm-asoc-plugin/blob/master/pom.xml#L4" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fibm-asoc-plugin%2Fblob%2Fmaster%2Fpom.xml%23L4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZcTV2PhMh-WXQWy_U7s3MgSuWZg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fibm-asoc-plugin%2Fblob%2Fmaster%2Fpom.xml%23L4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZcTV2PhMh-WXQWy_U7s3MgSuWZg&#39;;return true;">https://github.com/jenkinsci/ibm-asoc-plugin/blob/master/pom.xml#L4

This will update the display name but not the artifact ID, i.e. it will still show up in URLs like the plugin site

Other than that I  think you need to publish a new version that has an administrative monitor / log messages telling users to migrate to the new one

Thanks
Tim

On Wed, 9 Oct 2019 at 09:55, Matt Murphy <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="PMh1krtuCwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">matthe...@...> wrote:

I’m the maintainer for the the <a href="https://plugins.jenkins.io/ibm-application-security" style="color:rgb(149,79,114)" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fibm-application-security\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHpLt-CCDtoj0CVmTzgUBxsMNRjnw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fibm-application-security\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHpLt-CCDtoj0CVmTzgUBxsMNRjnw&#39;;return true;">IBM Application Security on Cloud plugin.  The cloud service that this plugin interacts with is no longer owned by IBM, so I’d like to rename the plugin.  I don’t want to publish a new plugin with the new name because that would force users to reconfigure their jobs.

 

I tried searching for steps to accomplish this, but I haven’t found anything.  Is it possible to rename a plugin (including changing the groupId)?

 

Thanks for your help.


--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="PMh1krtuCwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/03b18a1c-c072-4cc1-8bd4-868d4768f60b%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/70b33099-1bc5-45d2-adc5-092830af1b03%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Daniel Beck
In reply to this post by Matt Murphy


> On 9. Oct 2019, at 16:47, Matt Murphy <[hidden email]> wrote:
>
> That's an interesting idea regarding having the new plugin depend on the old one

The other way around, so any users who update the old plugin get the new one as a dependency (it must not be allowed to dynamically load though).

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/13D8D707-76F8-4ABA-BAE9-F9C151630B6E%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: How to rename a Jenkins plugin?

Matt Murphy
I see.  That makes sense.  Thanks.

On Wednesday, October 9, 2019 at 11:34:42 AM UTC-4, Daniel Beck wrote:


> On 9. Oct 2019, at 16:47, Matt Murphy <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="TOlrgm12CwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">matthe...@...> wrote:
>
> That's an interesting idea regarding having the new plugin depend on the old one

The other way around, so any users who update the old plugin get the new one as a dependency (it must not be allowed to dynamically load though).

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f1f7a12a-a291-46d9-89c6-92ff9764dd74%40googlegroups.com.