http://stats.jenkins-ci.org/jenkins-stats/svg/201312-jenkins.svg
1.544 has 8286 installations 1.532.1 has 1174 installations 1.509.4 has 2257 installations 1.509.2 has 1035 installations 1.480.3 has 571 installations 1.466.2 has 352 installations 1.447.2 has 69 installations 1.424.6 has 527 installations (some hold-outs here) I haven't done a running total summation, but as a rough guess I would estimate 1.509 as being a good parent version to pick at present... probably less than ~3000 Jenkins installations out of 72000 will be unable to install is you use 1.509 as your base version and you'll get good API coverage If you are happy appealing to only ~65% (my guess from the feel of the graph, but do a real calculation if you are using this) of Jenkins installations you could be aggressive and pick 1.532 On 7 January 2014 10:24, Stephen Connolly <[email protected]>wrote: > I will probably bump credentials up past 1.424 in the near future... I > have yet to decide on the minimum version to bump to... I think it will > have to be post 1.480 though as there are some UI glitches that are only > fixable in newer Jenkins versions... and it is those UI glitches that will > drive the release. > > With the credentials plugin, my main driver is to get it as feature > complete as I can without delivering a fundamentally broken UI on common > versions of Jenkins. Once adding new features is less of a priority or once > I hit a critical UI issue, then I will bump the minimum version to the > lowest version that fixes the issue... if that version happens to be one > that is still covered by my employers support terms, well and good, but if > it means that some versions covered by my employers are not compatible... > well that is the way the cookie crumbles, and users of older versions > should still have a very feature rich experience. > > For the OP's case, I would take a look at the latest jenkins statistics > and see what version is the cut-off for 80-90% of jenkins installs, and > pick the highest LTS <= that cut-off... then depending on your API > requirements, start bumping up in LTS versions until you get the API > features you require > > > On 7 January 2014 02:47, Daniel Beck <[email protected]> wrote: > >> On 06.01.2014, at 21:37, Ulli Hafner <[email protected]> wrote: >> >> > rather than using the latest I would suggest to use the smallest >> version that compiles (or works) with the plug-in. >> >> Another downside of using older versions of Jenkins (especially 1.466 or >> older) as base is that the plugin will then be considered to have >> dependencies to plugins that were extracted from core in the meantime. This >> makes plugin management quite a bit more difficult for Jenkins admins. Yes, >> it's nice that the Credentials plugin (1.9.1) only requires 1.424, but in >> Jenkins 1.532.1, it appears to have six plugin dependencies (ant, javadoc, >> external-monitor-job, ldap, pam-auth, and mailer). Which of those are real? >> Are _any_ of those real dependencies? Timestamper got rid of its >> dependencies to external-monitor-job, ldap, pam-auth and mailer between >> 1.5.7 to 1.5.8. How? The Jenkins base version was updated from 1.461 to >> 1.520… >> >> Relevant part in Jenkins core source code: >> >> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/ClassicPluginStrategy.java#L265 >> >> So from the POV of a Jenkins admin who's mostly on the newest LTS >> release, I'd consider a base version of 1.509[.x] to be great, 1.480[.x] >> OK, and anything older to just be cumbersome when trying to determine which >> plugin is actually required by which other plugin. >> >> --- >> >> Here's the current version distribution of installations that provide >> anonymous usage data. This can also help you determine how important it is >> for you to support older versions of Jenkins: >> http://stats.jenkins-ci.org/jenkins-stats/svg/201312-jenkins.svg >> >> The following table shows when the various LTS releases were released to >> give you an idea how old they are: >> http://mirrors.jenkins-ci.org/war-stable/ >> >> -- >> 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. >> > > -- 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.
