On Tue, Mar 1, 2016 at 12:20 PM, Kohsuke Kawaguchi <k...@kohsuke.org> wrote: > I was under the assumption that you want > to maintain the current trinity
Yes. > in which case the only place it can go > would be another plugin. Well, split across the existing ones, according to API structure. > But you seem to be saying that they should all go to github-branch-source. > That is, that plugin will get such dependencies like pipeline-mutlibranch > and branch-api. I have no problem with it, but I just want to make sure I > understand you correctly. No you did not. > Also, thanks for pointing out MultiBranchProjectFactory.createProject, but > WorkflowMultiBranchProjectFactory.doCreateProject doesn't use it at all > today, and even if that code is made to understand some attributes, one can > only do what this plugin anticipates. Attributes for various things (folder icon, etc.) would need to be defined in the API. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1hU3yxHK5f_jVmLo%3Dn31RuB7265Uuwf8bEc_Cqps%3D%2BCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
