[JIRA] (JENKINS-4021) TFS - unparseable date problem
justinas Urbanavicius commented on JENKINS-4021 TFS - unparseable date problem Any progress on this issue ? having the same problem on windows 2008 server with Jenkins 1.5 and latest plugin version. 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/groups/opt_out.
[JIRA] (JENKINS-4021) TFS - unparseable date problem
redsolo commented on JENKINS-4021 TFS - unparseable date problem I dont think ignoring the date is a solution, but perhaps as David mentioned there could be an option where a custom locale can be configured at system- or project-level. This locale caould then be used for parsing the dates, overriding the guessing that the plugin has to do due to the output of the tf tool. Unless noone knows of a way to override the system regional setting a command prompt? 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
[JIRA] (JENKINS-4021) TFS - unparseable date problem
Mikael Floberg commented on JENKINS-4021 TFS - unparseable date problem This happened to me as well. I am voting for a fix. Now I have to change the SERVER local and that is not the correct way. 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
[JIRA] (JENKINS-4021) TFS - unparseable date problem
redsolo commented on JENKINS-4021 TFS - unparseable date problem I have looked into this issue before and I think that it is impossible to evaluate the date from java. Something to do with the locale that the slave /master is running. Mikael could you try to get the locale that is active in the jvm that is running? And if its possible, an example output that the plugin cannot parse? I think the problem is with the tfs tool that generates a locale based date... 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
