On Fri, Sep 5, 2014 at 11:58 AM, Tom Fennelly <[email protected]> wrote: > what is the conceptual "line" between AbstractBuild and Run (and between > AbstractProject and Job)? When someone needs to add something new to these > core APIs, what are the things that make you decide to put it in one or the > other (AbstractBuild or Run or AbstractProject or Job)
I do not think there is any very clear conceptual distinction, at least historically; Kohsuke just kind of moved some stuff around in the class hierarchy for various purposes. :-) Also bear in mind that by the time you saw the “distinction” I had already pulled quite a bunch of stuff out of AbstractBuild/Project that did not really need to be there (LazyBuildMixIn, ParameterizedJobMixIn, and many smaller things). I see https://github.com/tfennelly/jenkins/commits/more-run-job-generalizations but (unless this is already in a PR) the more useful link is: https://github.com/tfennelly/jenkins/compare/more-run-job-generalizations -- 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/d/optout.
