[JIRA] [tfs] (JENKINS-4021) TFS - unparseable date problem
Mats Taraldsvik commented on JENKINS-4021 TFS - unparseable date problem @Justinas Urbanavicius: Sure, a brute-force solution might be a bad idea. However, the example proves that the dates are parseable. Setting the preferred/correct locale in the Jenkins TFS Plugin's configuration is a viable solution imho, changing the TFS Server configuration is not. 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] [tfs] (JENKINS-4021) TFS - unparseable date problem
Mats Taraldsvik commented on JENKINS-4021 TFS - unparseable date problem I looked at this error a while ago, and the best solution I could come up with, was to try parsing the date with all locales on the system. This could be a pretty safe fallback, with optional user configurable locale in the TFS plugin configuration settings. Look at this ideone snippet where I took the current date parsing function and modified it to the proposed behaviour: http://ideone.com/VPqO8e I hope this can be implemented, and solve this bug in most cases (but some might have to configure the locale explicitly). 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] [tfs] (JENKINS-4021) TFS - unparseable date problem
Justinas Urbanavicius commented on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. 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] [tfs] (JENKINS-4021) TFS - unparseable date problem
Justinas Urbanavicius edited a comment on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. In some cases, then your build system is set up on a different environment, you might not even have the same locales, like building on Linux for example. 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.
