On Tuesday, March 10, 2020 at 3:21:34 AM UTC-6, James Nord wrote: > > > Skip labels provided by parents - When a plugin depends on another > plugin, the dependency will be installed automatically. A label is not > required on the dependency if the consuming plugin has the label > > but if the parent can be used without the child (extension) then how does > that parent get found in isolation. The only case of not labelling the > parent is when it provides no user feature in my opinion (eg it's a pure > api plugin) >
What I was envisioning was: Bitbucket Branch Source plugin depends on git plugin. Bitbucket Branch Source plugin would be labeled 'bitbucket'. Git plugin would not be labeled 'bitbucket' because it will be installed automatically when Bitbucket Branch Source is installed. Git plugin depends on git client plugin. Git plugin would be labeled 'git'. Git client plugin would not be labeled 'git' because it will be installed automatically when Git plugin is installed. Git client plugin is an example of a pure API plugin and would have very few labels. I think the Bitbucket Branch Source -> Git plugin case is an example of your concern for locating a plugin in isolation. In that case, a search for the 'bitbucket' label will not show the git plugin. I was assuming that a Bitbucket user will prefer to install one of the higher level integrations (Bitbucket plugin, Bitbucket Branch Source plugin, Bitbucket Pullrequest BUilder, Bitbucket Server Notifier, etc.) and will receive the git plugin and the git client plugin as dependencies because they chose one or more of the higher level integration plugins. Did I understand your concern? -- 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/15ff8d35-054e-4162-a1c3-6cef6714b032%40googlegroups.com.
