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.
