|
||||||||
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-12908) TFS errors during get oper... j...@olsonzoo.com (JIRA)
- [JIRA] (JENKINS-12908) TFS errors during get... reds...@java.net (JIRA)
- [JIRA] (JENKINS-12908) TFS errors during get... j...@olsonzoo.com (JIRA)
The code behind the execution of the TFS command line will check if the tf tool returns with 1 or 0, and those are marked as success. My guess is that the tf command line tool returned either 1 or 0 regardless of the errors. That makes it somewhat difficult for the jenkins plugin to know if there was a problem or not. If the authentication fails, then tf returns with the code 100 and thus the plugin fails the build.
I reccon I could do some parsing of the console output that the TFS tool generates and fail the build if it finds anything resembling such a problem. But that would not be possible for the history command, because if someone checks in a comment resembling the text the plugin will look for then the plugin would fail the build for no good reason.
Does this happen a lot for you?