[JIRA] (JENKINS-59136) Deprecate plugins and provide suggestions to user

[josephp90@gmail.com (JIRA)]

Joseph Petersen created an issue

Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Issue Type: Epic Assignee: Joseph Petersen Components: core Created: 2019-08-29 01:29 Priority: Minor Reporter: Joseph Petersen Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as Auto uninstall upstream service dependency is gone and plugin is useless. Auto uninstall based on version of another plugin (you have moved logic from one to another) Auto uninstall tombstone plugins Auto uninstall due to security reasons Suggest uninstall for security reasons Suggest uninstall for any reason Recommend using another plugin URL pointing to documentation for the recommendation  In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: https://github.com/Argelbargel/gitlab-branch-source-plugin https://github.com/jenkinsci/gitlab-branch-source-plugin Suggest upgrading due to changes upstream services Auto upgrade due to changes to upstream service Feel free to add bullets or comments with suggestions. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[josephp90@gmail.com (JIRA)]

Joseph Petersen updated an issue

Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user

Change By: Joseph Petersen

Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as

* Auto uninstall upstream service dependency is gone and plugin is useless. * Auto uninstall based on versions of other plugins (you have moved logic from area to another area of plugins) ** configuration-as-code-plugin is a good example of this. JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials plugin So a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin * Auto uninstall tombstone plugins * Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation  ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: [https://github.com/Argelbargel/gitlab-branch-source-plugin] [https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service * Implied suggested upgrade depending on matrix of plugins and their version? ** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault plugin It would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] *

Feel free to add bullets or comments with suggestions.

Add Comment

[josephp90@gmail.com (JIRA)]

Joseph Petersen updated an issue

Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Change By: Joseph Petersen

Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as * Auto uninstall upstream service dependency is gone and plugin is useless.

* Auto uninstall based on version versions of another plugin other plugins (you have moved logic from one area to another area of plugins ) * * configuration-as-code-plugin is a good example of this.

JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials plugin So a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin *

Auto uninstall tombstone plugins

* Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation  ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: [https://github.com/Argelbargel/gitlab-branch-source-plugin] [https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service

* Implied suggested upgrade depending on matrix of plugins and their version? ** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault plugin It would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] * Feel free to add bullets or comments with suggestions.

Add Comment

[josephp90@gmail.com (JIRA)]

Joseph Petersen updated an issue

Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Change By: Joseph Petersen

Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as * Auto uninstall upstream service dependency is gone and plugin is useless.

* Auto uninstall based on versions of other plugins (you have moved logic from area to another area of plugins) ** configuration-as-code-plugin is a good example of this.

JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials plugin So a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin * Auto uninstall tombstone plugins * Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation  ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: [https://github.com/Argelbargel/gitlab-branch-source-plugin] [https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service

* Implied suggested upgrade depending on matrix of plugins and their version with some conditions ?

** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault plugin It would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] * Feel free to add bullets or comments with suggestions.

Add Comment

[josephp90@gmail.com (JIRA)]

Joseph Petersen assigned an issue to Joseph Petersen

Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user

Change By: Joseph Petersen Assignee: Joseph Petersen (old)

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)