I am starting on my first plugin. but I can't quite figure out the parts..
how do tell the global configuration code (shows up in Jenkins Configure System) from the Job code stuff that appears independent of Job step (or post job step). I see the jelly parts, I just can't tie that to code yet.. I've loaded the source for other plugins for learning, but this part is still escaping me. the extending Architecture words don't add anything. I don't see the inheritance tree. and why would I choose one approach vs another. I do get that a plugin can provide additional extension points for other downstream plugins to leverage so a single inheritance chart can't show everything I see some plugins subclass Builder, some see to go right to a lower subclass (Notifier, publisher, recorder,...) then I see things like FTPPublisher, can 'add' a new entry in its post build step. I see the code, and I see the delete button on the config.jelly file, but I don't see the Add button. so it must have been a documented side effect of something.. but I can't find that. I don't find any good doc/javadoc on the Jenkins use of Jelly. because there are so many other plugins, a lot of folks have gone thru this startup process. what am I missing? I can maven build the sample, and any plugin I download, and can run it both standalone and thru my running jenkins. I have a whole build tree of jobs that run and work fine (on agents on different operating systems all virtual machines).. but I want another function.. so why not learn how to extend it?! (and I use eclipse and m2e). thanks for any guidance -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
