> > 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. All projects that i know that started with “groups” (+ sub-groups) end with “tags”, because groups can’t be applied for all cases. Soft dependencies with reverse dependencies can also provide better user experience. Is it possible to implement them?
-- 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/2E72A05D-AE04-465B-9160-C64AC9CAA4AF%40gmail.com. For more options, visit https://groups.google.com/d/optout.
