|
||||||||
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)
Hi Rob,
coverity is a static analysis tool. In normal usage (outside of Jenkins), the coverity binary is prepended to the normal build command line.
e.g. "cov-build g++ foo.cc".
I'm not familiar with the specifics of how plugins interact with Jenkins, but it looks like the coverity plugin has some classes which inherit from LauncherDecorator, these prepend "cov-build " to the command, when the LauncherDecorator::decorate() method is called. It seems like it is doing this for every command, when it should just be done for the build commands.
Anyway, thanks for fixing the login parsing. I will test the fix and if it doesn't work I'll stick with the workaround.