|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
Hi everyone,
we are currently running Jenkins ver. 1.535 and experiencing this issue as well. Now that LTS 1.532.1 has been released on 25th of Nov, I am wondering if this fix has been integrated. The issue
JENKINS-19352is not mentioned in the changelog (http://jenkins-ci.org/changelog-stable).Maybe I am missing the information for some reason so I'd be grateful if someone could point out if LTS 1.532.1 includes this fix. Or, if not, if there will be a LTS release in the foreseeable future.
Thanks for all the efforts