|
||||||||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Again: Nobody cares about 1.466 anymore. It has been out of community support for years. Out of 103,900 known installs of Jenkins, 101,200 use a more recent version of Jenkins.
So unless you can show that the issue still occurs on 1.596.x, or 1.607, we don't care as far as this being a bug of some kind goes.
Feel free to ask for advice on the jenkinsci-users mailing list, but given how few users of that version are still around, it's doubtful anyone can help you with it.