[JIRA] (JENKINS-15862) perforce session ticket is not always parsed correctly
Tim Mason commented on JENKINS-15862 perforce session ticket is not always parsed correctly 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. 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 ticket is not always parsed correctly
Tim Mason updated JENKINS-15862 perforce session ticket is not always parsed correctly Change By: Tim Mason (19/Nov/12 12:19 PM) Description: The perforce plugin does not always parse the session ticket from "p4 login -p" correctly, causing the job to fail.I noticed this when using the coverity plugin in combination with the perforce plugin. The coverity plugin causes some extra text to be emitted from the "p4 login -p" command, which seems to confuse the parser in the perforce plugin.Example of the extra text:timm@daxtsmtf02> cov-build --dir foo p4 login -pEnter password: 53637D707C9CB35CF2436B90972121A0[WARNING] No files were emitted. This may be due to a problem with your configurationor because no files were actually compiled by your build command.Please make sure you have configured the compilers actually used in the compilation. For more details, please look at: /home/timm/foo/build-log.txttimm@daxtsmtf02>When this happens in Jenkins, it looks like the perforce plugin is just taking the last line of output (instead of the second line) as the session ticket. Example from Jenkins console log:[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 workspace -o MTFRA_ME_static_analysis[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 login -p[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 -P "/userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp/build-log.txt" workspace -o MTFRA_ME_static_analysisCaught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset.I managed to workaround this problem by adding an option the coverity plugin which suppress the output of the extra text. But it is not ideal as the extra text is actually a warning message which might be useful at other stages in the build, and I have to suppress it for all stages.Note: there is a related ticket open against the coverity plugin (JENKINS-14834) which says the coverity plugin should not be active during the pre-build steps. If that was fixed, it would resolve this issue. But I opened this ticket for the perforce plugin as I think an improvement in the way the perforce plugin gets the session ticker ticket would be a good change to make. 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 ticket is not always parsed correctly
Tim Mason created JENKINS-15862 perforce session ticket is not always parsed correctly Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: perforce Created: 19/Nov/12 12:15 PM Description: The perforce plugin does not always parse the session ticket from "p4 login -p" correctly, causing the job to fail. I noticed this when using the coverity plugin in combination with the perforce plugin. The coverity plugin causes some extra text to be emitted from the "p4 login -p" command, which seems to confuse the parser in the perforce plugin. Example of the extra text: timm@daxtsmtf02> cov-build --dir foo p4 login -p Enter password: 53637D707C9CB35CF2436B90972121A0 [WARNING] No files were emitted. This may be due to a problem with your configuration or because no files were actually compiled by your build command. Please make sure you have configured the compilers actually used in the compilation. For more details, please look at: /home/timm/foo/build-log.txt timm@daxtsmtf02> When this happens in Jenkins, it looks like the perforce plugin is just taking the last line of output (instead of the second line) as the session ticket. Example from Jenkins console log: [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 workspace -o MTFRA_ME_static_analysis [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 login -p [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 -P "/userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp/build-log.txt" workspace -o MTFRA_ME_static_analysis Caught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset. I managed to workaround this problem by adding an option the coverity plugin which suppress the output of the extra text. But it is not ideal as the extra text is actually warning message which might be useful at other stages in the build, and I have to suppress it for all stages. Note: there is a related ticket open against the coverity plugin (JENKINS-14834) which says the coverity plugin should not be active during the pre-build steps. If that was fixed, it would resolve this issue. But I opened this ticket for the perforce plugin as I think an improvement in the way the perforce plugin gets the session ticker would be a good change to make. Environment: RedHat EL 5.5 Project: Jenkins Priority: Major Reporter: Tim Mason 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-15419) TAP published results hide JUnit published results
Tim Mason commented on JENKINS-15419 TAP published results hide JUnit published results Hi Bruno, thanks for the fix 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-15419) TAP published results hide JUnit published results
Tim Mason created JENKINS-15419 TAP published results hide JUnit published results Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 05/Oct/12 11:58 AM Description: Hello, I had a job with some unit tests which give results in Junit. I published the results using "Publish JUnit test result report" in post-build actions, and it worked fine. Then I added separate build step with different unit tests, which give results in TAP format. I installed the TAP plugin and added "Publish TAP results" in post-build actions. Now, I can only see results from the TAP tests. JUnit tests seem to have vanished. Any idea what is wrong? Project: Jenkins Priority: Major Reporter: Tim Mason 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-15419) TAP published results hide JUnit published results
Tim Mason updated JENKINS-15419 TAP published results hide JUnit published results Change By: Tim Mason (05/Oct/12 11:59 AM) Description: Hello,I had a job with some unit tests which give results in Junit JUnit . I published the results using "Publish JUnit test result report" in post-build actions, and it worked fine. Then I added separate build step with different unit tests, which give results in TAP format. I installed the TAP plugin and added "Publish TAP results" in post-build actions. Now, I can only see results from the TAP tests. JUnit tests test results seem to have vanished.Any idea what is wrong? 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason assigned JENKINS-15336 to Josh Vinson Provide sample jelly template for including results from coverity plugin in email Hi Josh, assigning this to you. Change By: Tim Mason (27/Sep/12 1:56 PM) Assignee: Josh Vinson 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason assigned JENKINS-15336 to Unassigned Provide sample jelly template for including results from coverity plugin in email Change By: Tim Mason (27/Sep/12 1:54 PM) Assignee: Tim Mason 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason commented on JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email Sure. Sorry, I intended this request to go to the maintainers of the coverity plugin, rather than email-ext. Could you assign it to them? 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-15336) Provide sample jelly template for including results from coverity plugin in email
Tim Mason created JENKINS-15336 Provide sample jelly template for including results from coverity plugin in email Issue Type: Improvement Assignee: Slide-O-Mix Components: coverity, email-ext Created: 27/Sep/12 1:20 PM Description: It would be nice if there was a sample jelly template that showed how to get results from the coverity plugin into an email. Something similar to the static-analysis.jelly file that is included with the email-ext plugin. Project: Jenkins Priority: Major Reporter: Tim Mason 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-13952) Coverity plugin cannot connect to CIM instance
[ https://issues.jenkins-ci.org/browse/JENKINS-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Mason resolved JENKINS-13952. - Resolution: Incomplete Jenkins was using OpenJDK, seems like the Coverity plugin doesn't like this. I change to Sun JDK and the plugin worked OK. So although there might be a bug somewhere, I am happy to close this issue as the problem is resolved. > Coverity plugin cannot connect to CIM instance > -- > > Key: JENKINS-13952 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13952 > Project: Jenkins > Issue Type: Bug > Components: coverity >Reporter: Tim Mason > > Hi, > I installed the coverity plugin. > On the Jenkins Configure System, after I enter the details for the Coverity > CIM instance and click the Check button, I get "unexpected error occurred". > Clicking Show Details gives the following: > java.lang.NoClassDefFoundError: Could not initialize class > com.sun.xml.wss.impl.SecurableSoapMessage > at > com.sun.xml.wss.ProcessingContext.setSOAPMessage(ProcessingContext.java:223) > at > com.sun.xml.wss.impl.misc.XWSSProcessor2_0Impl.createProcessingContext(XWSSProcessor2_0Impl.java:153) > at > jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:97) > at > jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:40) > at > com.sun.xml.internal.ws.handler.HandlerProcessor.callHandleMessage(Unknown > Source) > at > com.sun.xml.internal.ws.handler.HandlerProcessor.callHandlersRequest(Unknown > Source) > etc > Any idea how I can fix this? > Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13952) Coverity plugin cannot connect to CIM instance
[ https://issues.jenkins-ci.org/browse/JENKINS-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163323#comment-163323 ] Tim Mason commented on JENKINS-13952: - Jenkins version is 1.466. I got same error with coverity plugins 1.1.3 and 1.1.4 > Coverity plugin cannot connect to CIM instance > -- > > Key: JENKINS-13952 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13952 > Project: Jenkins > Issue Type: Bug > Components: coverity >Reporter: Tim Mason > > Hi, > I installed the coverity plugin. > On the Jenkins Configure System, after I enter the details for the Coverity > CIM instance and click the Check button, I get "unexpected error occurred". > Clicking Show Details gives the following: > java.lang.NoClassDefFoundError: Could not initialize class > com.sun.xml.wss.impl.SecurableSoapMessage > at > com.sun.xml.wss.ProcessingContext.setSOAPMessage(ProcessingContext.java:223) > at > com.sun.xml.wss.impl.misc.XWSSProcessor2_0Impl.createProcessingContext(XWSSProcessor2_0Impl.java:153) > at > jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:97) > at > jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:40) > at > com.sun.xml.internal.ws.handler.HandlerProcessor.callHandleMessage(Unknown > Source) > at > com.sun.xml.internal.ws.handler.HandlerProcessor.callHandlersRequest(Unknown > Source) > etc > Any idea how I can fix this? > Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13952) Coverity plugin cannot connect to CIM instance
Tim Mason created JENKINS-13952: --- Summary: Coverity plugin cannot connect to CIM instance Key: JENKINS-13952 URL: https://issues.jenkins-ci.org/browse/JENKINS-13952 Project: Jenkins Issue Type: Bug Components: coverity Reporter: Tim Mason Hi, I installed the coverity plugin. On the Jenkins Configure System, after I enter the details for the Coverity CIM instance and click the Check button, I get "unexpected error occurred". Clicking Show Details gives the following: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.wss.impl.SecurableSoapMessage at com.sun.xml.wss.ProcessingContext.setSOAPMessage(ProcessingContext.java:223) at com.sun.xml.wss.impl.misc.XWSSProcessor2_0Impl.createProcessingContext(XWSSProcessor2_0Impl.java:153) at jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:97) at jenkins.plugins.coverity.ClientAuthenticationHandlerWSS.handleMessage(ClientAuthenticationHandlerWSS.java:40) at com.sun.xml.internal.ws.handler.HandlerProcessor.callHandleMessage(Unknown Source) at com.sun.xml.internal.ws.handler.HandlerProcessor.callHandlersRequest(Unknown Source) etc Any idea how I can fix this? Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
