Thanks for the clarification. If newer API support is needed, then the plugin must depend on the version which supports that API. You've adapted the git plugin to the newer SCM API on the master branch, and have offered it as a 2.3 beta pre-release.
I don't understand how to use the LTS update center, and how to push a plugin release to the LTS update center separately from the standard update center. Can you point me to a description of the technique? Doesn't that also mean that once 2.3 is released, Jenkins versions prior to the release of that new API won't be able to use the git plugin? That seems like it would be really bad, since the git plugin seems to be installed on roughly half the Jenkins installations. Thanks, Mark Waite On Fri, Aug 1, 2014 at 10:09 AM, Jesse Glick <[email protected]> wrote: > On Thu, Jul 31, 2014 at 3:24 AM, Stephen Connolly > <[email protected]> wrote: > > So for example there are some changes to the SCM api in 1.568... if you > want > > to pick up support for them then there is really only one way to do > that... > > In fact the master branch of git-plugin does require 1.568+ for this > reason; the 1.509+ support with some cherry-picked fixes remains in > the 2.2.x branch. Since there is not yet an LTS ≥1.568 the master > releases are marked 2.3-beta-x. (Again not strictly necessary since > LTS has its own UC as Stephen noted.) > > -- > 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. > -- Thanks! Mark Waite -- 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.
