[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus closed an issue as Duplicate Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Change By: Baptiste Mathus Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Seems like Tyler actually filed JENKINS-53256 two days. Going to close this in favor of this older reported issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml BTW, R. Tyler Croy what are you thoughts about that. Somehow as a followup to our discussioon yesterday, did you mean you think we should actually remove any plugin that is not explictly listed in essentials.yaml, or should we support adding some specific delete field or so? (I guess the former, but better check ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Another obvious case is for instance the maven-plugin: right now, for historical reasons, it is installed because pulled in by many plugins. But we filter out its descriptor, hence it's not even visible from the UI. So if some day we were able to break those transitive dependencies, it would be nice to be able to uninstall it seamlessly from instances running out there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 08:20 Priority: Major Reporter: Baptiste Mathus Issue We currently support only adding plugins, by enriching essentials.yaml. We cannot remove plugins (or anything). With the recent rebrand, it would have come handy to be able to remove a given plugin. In that case, it was a simple rename. But there could more convoluted cases, with plugin split, a better one to achieve some feature, etc. Expected As Evergreen developers, we want to be able to instruct that a given (set of) plugin(s) be uninstalled to cover our various use cases Add Comment
