Renaming a plugin

[Marit M]

Hello,

Is there a way to rename a plugin after it's already published?

Thanks,

Marit. 

[Alexander Brandes]

Hey,

take a look at the RPU documentation how to do that.

Best,

Alex

[Jesse Glick]

On Sun, Dec 18, 2022 at 7:47 AM Alexander Brandes <mc.ca...@gmail.com> wrote:

take a look at the RPU documentation how to do that.

I think this doc should be made to emphasize that you really really should not ever do this unless you are pretty sure your plugin has no users under its existing name.

Changing the `name` (display name) is fine at any time. Changing the `groupId` will break any Maven dependencies from other plugins, which may or may not be an issue. But changing the `artifactId` means changing the identifier by which the Jenkins plugin manager differentiates this plugin from others, and will cause mayhem for users who have already installed it under the old name.

[Alexander Brandes]

Great idea! I rejected PRs attempting to modify their path before.

I submitted https://github.com/jenkins-infra/repository-permissions-updater/pull/3047 to make it obvious that altering specific components is highly discouraged.

[Marit M]

I'm pretty sure that the plugins have no users.

Can you please guide how to do it, or maybe make the necessary changes in a different branch?

The plugins that needs to be changed are:

• BMC DevOps for CFA  >>>>> BMC AMI DevOps for Application Checkpoint Analysis - 0 installs
• BMC DevOps for AMI Change Manager for IMS TM >>>>> BMC AMI DevOps for Change Manager for IMS TM - 2 installs

Thank you,

Marit.

ב-יום רביעי, 21 בדצמבר 2022 בשעה 22:23:07 UTC+2, mc.ca...@gmail.com כתב/ה:

[Gavin Mogan]

If it has spaces it's just the pretty name.

You can rename it with the <name> section of pom.xml then do a new release 

--
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/7f213569-8614-4223-839b-e8e106829ad8n%40googlegroups.com.

[Marit M]

I changed the name, and I would still like to change the artifactId as well.

Please advise the steps that should be taken.

Thanks,

Marit.

ב-יום רביעי, 28 בדצמבר 2022 בשעה 18:51:41 UTC+2, ga...@gavinmogan.com כתב/ה:

[Daniel Beck]

On Fri, Dec 30, 2022 at 7:51 AM Marit M <mar...@gmail.com> wrote:

I changed the name, and I would still like to change the artifactId as well.

Please advise the steps that should be taken.

You shouldn't, see https://github.com/jenkins-infra/repository-permissions-updater#changing-plugin-id

If you _really_ want to: It's a new, different plugin. Start over, creating a new plugin with the new name. Copy all code over. Change the package name, so the fully qualified class names are different (perhaps use this opportunity for a little cleanup of backwards compatibility code). Mark the old plugin as deprecated. Think about the expected behavior when both plugins are installed, in particular any configuration/data migration (or don't and let users reconfigure everything). Consider creating an administrative monitor requesting that users uninstall the old plugin if both the old and new plugin are installed and enabled. This gets even more difficult if any other plugins declare a dependency on the obsolete one.

This is really hard to do well, and I don't think it has been done in a long time in any plugin that can be considered even a little popular. All of the old Pipeline-related plugins are still named "workflow-whatever" despite the user-visible name having changed six years ago.