Greetings, On Wed, Oct 9, 2013 at 1:23 AM, Daniel Beck <m...@beckweb.net> wrote: > It looks like you're referring to > https://issues.jenkins-ci.org/browse/JENKINS-19515 which will be fixed in > 1.509.4. There's already an RC, so you could try upgrading.
https://issues.jenkins-ci.org/browse/JENKINS-19515 is a fix for something introduced by https://issues.jenkins-ci.org/browse/JENKINS-16301 which itself is just a "poor performance" issue. I'm a bit conflicted on this, but I think a case could be easily made that performance fixes shouldn't be injected into an existing LTS line. Perhaps a new LTS, sure, but given that 16301 only seemed to affect artifacts in the 100s of megabytes range, I have doubts that this hits very many installations, and so its inclusion into LTS seems suspect. > Did you test the 1.509.3 RC when it was available for almost four weeks > before the final version was released? If I wanted to be in the RC testing game I would just use the RCs themselves. As I do for every Jenkins LTS, I deploy it locally on my laptop first and run about a dozen jobs for my most critical use cases. They all worked and I did not see this issue. This is way beyond what most users do! There seems to be very little value in having an LTS line at all if we're just going to off load extensive testing to the users again -- given your attitude, please tell me how this differs from the weekly releases? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
