I would even go a step further regarding plugins, the @Extension mechanism (on which plugins are based) is used internally quite a bit as well.
> Would you say that an external interface used by Jenkins is a link to a > source control management system (eg. GitHub) ? > > Another main principle in Jenkins architecture is the plugins system. Most > of the features are implemented by plugins, including those that interact > with external interfaces. For example, the interaction with maven, node, > git or mercurial is implemented by plugins. > > -- > >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/9abcbd2d-1898-4042-a28a-75bf620209a3%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/9abcbd2d-1898-4042-a28a-75bf620209a3%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/c6b7a41c-029e-4d33-9081-fc42ee8f8863%40googlegroups.com.
