|
||||||||||||||
|
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/d/optout.
Since nobody watching this provided additional information since I posted the previous comment, I'm resolving this as cannot reproduce.
If you experience this issue on a Jenkins release no older than eight weeks (LTS or latest&greatest), please file a new bug against core and include ALL the information asked for in the preceding comment.
In the preceding comment I also explain why this issue description and the comments are not useful in getting this issue resolved. In essence, too little real information is provided here, and comments seem to contradict, indicating different causes. Newly filed issues won't have this problem.
If you're using a version older than eight weeks, and cannot reproduce the problem (or did not try to do so) on a current Jenkins version, please refrain from filing a new issue. Many issues in Jenkins get fixed during normal development and it's a waste of time trying to investigate long resolved issues.