|
||||||||
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-15862) perforce session tic... tma...@nyx.com (JIRA)
- [JIRA] (JENKINS-15862) perforce sessio... tma...@nyx.com (JIRA)
- [JIRA] (JENKINS-15862) perforce sessio... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15862) perforce sessio... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15862) perforce sessio... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15862) perforce sessio... tma...@nyx.com (JIRA)
I don't know what coverity is, or how it's injecting itself in front of the p4 commands, but just taking the second line as you suggested should at least fix the ticket issue.
I am concerned, however, since the other command parsing algorithms are just as naive because we assume that we'll only ever be interacting directly with perforce. If the other commands throw similar 'junk' output, you will probably still run into other issues further down the line.