On Thu, Aug 27, 2015 at 11:37 AM, Gus Reiber <[email protected]> wrote: > "detached" plugins > that are essential to Jenkins but have been implemented as plugins for > quicker updates and ease of implementation.
Split plugins are just plugins, which by definition are not “essential” to Jenkins. They may be very useful and commonly desired, or they may be obscure, but you can always disable them. (Even bundled plugins, though these cannot be _uninstalled_.) > Of the optional, feature style plugins I.e., just “plugins”. I am not trying to split hairs here, but to emphasize again that split plugins deserve no special status when deciding which plugins ought to recommended to new users. Each plugin should be evaluated on its intrinsic merits, not historical inclusion in core sources. Some examples to illustrate my point: * `ssh-slaves` (split, currently bundled): used in most larger installations, probably good to recommend. * `windows-slaves` (split, currently bundled): useful in some Windows-based installations but often hard to troubleshoot compared to JNLP slaves; debatable. * `external-monitor-job` (split, currently bundled): somewhat exotic use case, probably best omitted. * `credentials` (dependency of splits, currently bundled): should be recommended to all users. * `git` (not currently bundled): good to recommend to new users, at least until we have an SCM selection wizard. * `chromedriver` (not currently bundled): useful for a small number of users, but too obscure to be recommended. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1gp9VGUkpw0P%2BKVd3iq7JNaY1%2BrWcZzesaGefTXJUCkA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
