one thing I never really got my head around was the API of the folders plugin. Many plugins could really improve if they would integrate properly with the folders plugin - but every time I started this, I gave up because it was not obvious how to do this. e.g. how to implement a config hierarchy on different levels: - global - folder - user - job
Domi On 17 Jul 2015, at 07:05, Daniel Beck <[email protected]> wrote: > > On 17.07.2015, at 01:13, John Tatum <[email protected]> wrote: > >> It seems like I had trouble finding good information about entry points. > > What do you mean by entry points? The ExtensionPoint/@Extension mechanism? > The Plugin class? @Initializer? Stapler request routing? Jelly > views/st:include? > >> It also did not seem like there were any references to the javadoc from the >> wiki(I always found what I needed using google). > > Is this related to using the Script Console? I'm asking because, when writing > plugins you should be able to configure your IDE to download and display the > Javadoc for Jenkins, so you should need the Javadoc on the web less. > > -- > 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/5048EC38-1E29-403B-88C1-290013F45FCE%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. -- 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/81B8AA9F-15B3-4D75-961F-0DC372CD8CD7%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
