On Tuesday, May 17, 2016 at 3:18:47 PM UTC-4, Daniel Beck wrote: > > > > On 17.05.2016, at 13:57, Ugo Bellavance <[email protected] <javascript:>> > wrote: > > > > Ok, but how can I apply a fix then? I've been told that my problem may > be caused by JENKINS-34213, this currently has a status of "Fixed". How > can I update my code to have the fix? > > > > It's in Jenkins 2.4. The fix is not yet available on the LTS release line. >
Ok, that is great, but when it will be available on the LTS line, will I be able to update my install from 1.656 to the version that will contain the fix (1.651.3 I guess)? Is there a way to be sure that JENKINS-34213 is the problem that I hit? I do have a heap dump and I've done some analysis on it, but it's a bit too complex for me at this point. Should I put the dump somewhere and ask for it to be analyzed in JENKINS-34213? Thanks, -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/24acc447-0cb3-431c-a90a-cc70b0b9d72d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
