On 25.09.2015, at 14:49, Tom Moore <[email protected]> wrote: > This is a great thread. I do want to raise one point though. This should > be a "clean" repacking and try to avoid inclusion of plugin functionality in > the install that may not be needed or desired. Your mentioning of Git for > example. Jenkins is used by people who utilize CVS, SVN, Git, Bazaar, Visual > Source Safe, Team Foundation Server, Perforce, etc, etc, etc. So > installation of Git as a default is not going to necessarily be something > desired by all. And none of these are even needed to run the base > application for configuration. > > I'd prefer identifying the plugin "groups" we know people will nearly always > use, such as a SCM, Authentication, or a Builder (Maven, MSBuild, Unity, etc) > and the first time a Jenkins server is started and the UI logged into then > the user is sent into a wizard to select the ones to download for the first > time. Obviously we wouldn't want to walk them through all 1100 plugins. > But I would think the three groups I mentioned would be pretty much a common > decision for nearly all installations.
This is actually something we're already discussing. https://groups.google.com/d/msg/jenkinsci-dev/kRobm-cxFw8/AQyLTVDSHQAJ The thread is a bit long, and started out completely differently, but may be worth reading. -- 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/288B59DF-C516-464B-B79A-642ADBCE31E7%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
