[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-03-17 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 1.9.0  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Change By: 
 Joel Briggs  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-03-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Cho Path: src/main/java/jenkins/plugins/coverity/CoverityLauncher.java src/main/java/jenkins/plugins/coverity/CoverityTool/CoverityCommand.java src/main/java/jenkins/plugins/coverity/CoverityTool/CoverityToolHandler.java src/main/java/jenkins/plugins/coverity/ws/DefectReader.java http://jenkins-ci.org/commit/coverity-plugin/7f5570f37a5c9b94d5da8edf9bececb1bdb8a56e Log: Merge branch 'BZ100126' into 'jenkins19' Fix for #100126 & #101120 #100126 - JENKINS-41138 Coverity - Job Failed.  With recent changes related to `CoverityLauncher`, `CoverityLauncherDecorator`, and all command classes, the intermediate directory was not setting up properly only when capturing the scripting languages.  #101120 - Null exception message when CIM information is blank. Added null checks and the coverity plugin does not throw any NPE exceptions. Also, added logging in the DefectReader. The result of the build with this change is pass as it was with previous version whether that is the correct behaviour or not. See merge request !87  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-03-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Cho Path: src/main/resources/jenkins/plugins/coverity/CoverityPublisher/help-isScriptSrc.html http://jenkins-ci.org/commit/coverity-plugin/a8360c5bb73396e9f037dc7a851f31eb1eea5766 Log: Merge branch 'BZ100126' into 'jenkins19' Fix for #100126 - JENKINS-41138 Coverity - Job Failed. Currently, we do not have enough information, which we asked the customer for more information to find the root cause of the problem, but have not heard back. However, with this changes, at least the users will know that if they want to capture and analyze scripting language source files, the files must exist in the build workspace. Fix: 100126 ![SupportScript_HelpText](/uploads/a5e152a7fab9bd392b6313b4760f4630/SupportScript_HelpText.jpg) See merge request !65  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-03-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Cho Path: src/main/java/jenkins/plugins/coverity/CoverityLauncher.java http://jenkins-ci.org/commit/coverity-plugin/94e32ea1d5978145b9275001962f4353676cd3c2 Log: JENKINS-41138 Coverity Job Failed. This is case when the Coverity plugin is used only for capturing scripting files. There was a problem with setting up the intermediate directory Fix: 100126  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-03-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Cho Path: src/main/resources/jenkins/plugins/coverity/CoverityPublisher/help-isScriptSrc.html http://jenkins-ci.org/commit/coverity-plugin/9b41dab5c2031e58d7541a46eaa1dbdf5e68c491 Log: JENKINS-41138 Coverity - Job Failed. Currently, we do not have enough information, which we asked the customer for more information to find the root cause of the problem, but have not heard back. However, with this changes, at least the users will know that if they want to capture and analyze scripting language source files, the files must exist in the build workspace. Fix: 100126  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-27 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 For both issues mentioned here, it seems that the file system capture was not enabled or working. If you can provide the console output logs and configuration it will be easier to determine if this is an issue with the plugin or a misconfiguration. (I'm looking for "--fs-capture-search" argument on the cov-build command with the $WORKSPACE directory value). Additionally, you could contact Coverity support to help assist you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- "1 Path"and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <- "2 Path"1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare result coverity-build(Jenkins Building result make intermediate folder) log with the "2 Path" but Building(Jenkins Building) reference with "1 Path"so build log content " Error: intermediate directory contains no translation units. " because analysis without build-objectI don't resolve this problem.(my effort to changing to the Coverity Intermdiate folder but I haven't)In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue (shotly sentence, Coverity analyze target folder different of the workspace folder)   and I have a tip (Jenkins Manage > Plug-in Manage > Delete the coverity Plug-in(version 1.8) > Coverity Plug-in downgrade 1.5 (Coverity Plug-in download version 1.5 coverity.hpi) > upload center) of resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 
 

[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- "1 Path"and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <- "2 Path"1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare result coverity-build(Jenkins Building result make intermediate folder) log with the "2 Path" but Building(Jenkins Building) reference with "1 Path"so build log content " Error: intermediate directory contains no translation units. " because analysis without build-objectI don't resolve this problem.(my effort to changing to the Coverity Intermdiate folder but I haven't)In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issueand I have a tip (Jenkins Manage > Plug-in Manage > Delete the coverity Plug-in (version 1.8)  > Coverity Plug-in downgrade 1.5 (Coverity Plug-in download version 1.5 coverity.hpi) > upload center) of resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   

[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- "1 Path"and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <- "2 Path"1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare result coverity-build(Jenkins Building result make intermediate folder) log with the "2 Path" but Building(Jenkins Building) reference with "1 Path"so build log content " Error: intermediate directory contains no translation units. " because analysis without build-objectI don't resolve this problem.(my effort to changing to the Coverity Intermdiate folder but I haven't)In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue and I have a tip (Jenkins Manage > Plug-in Manage > Delete the coverity Plug-in > Coverity Plug-in downgrade 1.5 (Coverity Plug-in download version 1.5 coverity.hpi) > upload center) of resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- "1 Path"and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <- "2 Path"1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare result coverity-build(Jenkins Building result make intermediate folder) log with the "2 Path" but Building(Jenkins Building) reference with "1 Path"so build log content " Error: intermediate directory contains no translation units. " because analysis without  build-  objectI don't resolve this problem. (my effort to changing to the Coverity Intermdiate folder but I haven't)   In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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 

[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- "1 Path"and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <- "2 Path"1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare  Result  result  coverity-build (Jenkins Building result make intermediate folder)  log with the "2 Path" but Building (Jenkins Building)  reference with "1 Path"so  build  log content " Error: intermediate directory contains no translation units. " because analysis without objectI don't resolve this problem.In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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, 

[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <-  "  1 Path " and after build make ajenkins\ $ {ITEM_ROOTDIR}\workspace\$ COV_IDIR <-  "  2 Path " 1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare Result coverity-build log with the "2 Path" but Building reference with "1 Path"so log content " Error: intermediate directory contains no translation units. " because analysis without objectI don't resolve this problem.In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- 1 Pathand after build make ajenkins\ ${ITEM_ROOTDIR}\workspace\$COV_IDIR <- 2 Path1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare Result coverity-build log with the "2 Path" but Building reference with "1 Path"so log content " Error: intermediate directory contains no translation units. " because analysis without objectI don't resolve this problem.In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path.See up to the Issue Description{color:red}{color:red}[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat{color}set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- 1 Pathand after build make a jenkins\  ${ITEM_ROOTDIR}\workspace\$COV_IDIR <- 2 Path1 & 2 Path in the "build-log.txt" compare with the build result "Failure"Compare Result coverity-build log with the "2 Path" but Building reference with "1 Path"so log content " Error: intermediate directory contains no translation units. " because analysis without objectI don't resolve this problem.In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8)Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-24 Thread csqe....@hanwha.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chang Seoun Cho commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I have a same issue. I think about this problem and than guessing the problem of a coverity intermediate folder path. See up to the Issue Description [C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-6535400382401528552.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1682811972736486368.bat] [Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1682811972736486368.bat set a C:\Program Files(x86)\Jenkins\coverity\temp-6535400382401528552.tmp <- 1 Path and after build make a $ {ITEM_ROOTDIR} \workspace\$COV_IDIR <- 2 Path 1 & 2 Path in the "build-log.txt" compare with the build result "Failure" Compare Result coverity-build log with the "2 Path" but Building reference with "1 Path" so log content " Error: intermediate directory contains no translation units. " because analysis without object I don't resolve this problem. In the Past Jenkins Version Update(1.6X -> 2.39) and than Coverity Plug-in update vesion(1.4 -> 1.8) Please I want to a resolve to the this Issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-23 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Shahar,  We can look into this issue (add internal bug to track), if you could provide an updated screenshots with the configuration you've run with and the updated console output that would be helpful. The Coverity tools scripting language support searches for files within the $WORKSPACE, so there would be an issues if you are expecting files outside of that location to be analyzed. (I noticed the plugin is missing hlep information on the "Support scripting language ..." option) Thanks, Joel  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-22 Thread shahar....@verint.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shahar Ron reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Change By: 
 Shahar Ron  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-20 Thread shahar....@verint.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shahar Ron commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 I did “Support scripting language sources during cov-build” but still receiving same error and warnings. for recognize python, i already did it as well...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-19 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Change By: 
 Joel Briggs  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Ken Dang Joel Briggs  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-19 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs edited a comment on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Hi  Sahar  Shahar ,You'll need to enable the “Support scripting language sources during cov-build” option in order for Coverity to attempt to capture and analyze python files. Also, you'll need to configure the coverity installation to recognize python (using `cov-configure --python`), if not already done so.Thanks,Joel  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-19 Thread jbri...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Briggs commented on  JENKINS-41138  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Job Failed   
 

  
 
 
 
 

 
 Hi Sahar, You'll need to enable the “Support scripting language sources during cov-build” option in order for Coverity to attempt to capture and analyze python files. Also, you'll need to configure the coverity installation to recognize python (using `cov-configure --python`), if not already done so. Thanks, Joel  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-17 Thread shahar....@verint.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shahar Ron updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Change By: 
 Shahar Ron  
 

  
 
 
 
 

 
 Using Coverity plugin to scan my *.py codes for the first time. Plugin was installed successfully and server configuration is valid.Once configured my first job to scan the code, im getting the below output:In addition, Coverity scan settings attached. {color:red}Checking Coverity configuration...[Stream] CoverityPlatform/Kruvi/Kruvi_001 : OK (version: 8.6.0)[Node] Jenkins : version 8.6.0Configuration is valid.Building in workspace C:\Program Files (x86)\Jenkins\workspace\Hostname[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp- 241874536621283803 6535400382401528552 .tmp, cmd, /c, call, C:\Windows\TEMP\ hudson1372423268953757710 hudson1682811972736486368 .bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\ hudson1372423268953757710 hudson1682811972736486368 .batCoverity Build Capture (64-bit) version 8.6.0 on Windows Server 2008 R2 Server Datacenter (full installation), 64-bit, Service Pack 1 (build 7601)Internal version numbers: 2d06cace01 p-kent1-push-26368.885.208C:\Program Files (x86)\Jenkins\workspace\Hostname> python -m compileall ./  C:\hostname\hostname.py  Listing ./ ...  Hello, world!   C:\Program Files (x86)\Jenkins\workspace\Hostname>exit 0 [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: C:/Program Files (x86)/Jenkins/coverity/temp- 241874536621283803 6535400382401528552 .tmp/build-log.txt[Coverity] cmd so far is: [C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze, --dir, C:\Program Files (x86)\Jenkins\coverity\temp- 241874536621283803 6535400382401528552 .tmp][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze" --dir "C:\Program Files (x86)\Jenkins\coverity\temp- 241874536621283803 6535400382401528552 .tmp"Coverity Static Analysis version 8.6.0 on Windows Server 2008 R2 Server Datacenter (full installation), 64-bit, Service Pack 1 (build 7601)Internal version numbers: 2d06cace01 p-kent1-push-26368.885.208Using 1 worker as limited by CPU(s)Looking for translation unitsError: intermediate directory contains no translation units.[Coverity] C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze returned 2, aborting...Build step 'Coverity' changed build result to FAILUREFinished: FAILURE{color}   please advise.  
 

  
 
 
 
 


[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-17 Thread shahar....@verint.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shahar Ron updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Change By: 
 Shahar Ron  
 
 
Attachment: 
 Capture.JPG  
 

  
 
 
 
 

 
 Using Coverity plugin to scan my *.py codes for the first time. Plugin was installed successfully and server configuration is valid.Once configured my first job to scan the code ,  im getting the below output: In addition, Coverity scan settings attached.  {color:red}Checking Coverity configuration...[Stream] CoverityPlatform/Kruvi/Kruvi_001 : OK (version: 8.6.0)[Node] Jenkins : version 8.6.0Configuration is valid.Building in workspace C:\Program Files (x86)\Jenkins\workspace\Hostname[C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-241874536621283803.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1372423268953757710.bat][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1372423268953757710.batCoverity Build Capture (64-bit) version 8.6.0 on Windows Server 2008 R2 Server Datacenter (full installation), 64-bit, Service Pack 1 (build 7601)Internal version numbers: 2d06cace01 p-kent1-push-26368.885.208C:\Program Files (x86)\Jenkins\workspace\Hostname>python -m compileall ./ C:\hostname\hostname.py Listing ./ ...C:\Program Files (x86)\Jenkins\workspace\Hostname>exit 0 [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: C:/Program Files (x86)/Jenkins/coverity/temp-241874536621283803.tmp/build-log.txt[Coverity] cmd so far is: [C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze, --dir, C:\Program Files (x86)\Jenkins\coverity\temp-241874536621283803.tmp][Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze" --dir "C:\Program Files (x86)\Jenkins\coverity\temp-241874536621283803.tmp"Coverity Static Analysis version 8.6.0 on Windows Server 2008 R2 Server Datacenter (full installation), 64-bit, Service Pack 1 (build 7601)Internal version numbers: 2d06cace01 p-kent1-push-26368.885.208Using 1 worker as limited by CPU(s)Looking for translation unitsError: intermediate directory contains no translation units.[Coverity] C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze returned 2, aborting...Build step 'Coverity' changed build result to FAILUREFinished: FAILURE{color} please advise.  
 

  
 
 
 
  

[JIRA] (JENKINS-41138) Coverity - Job Failed

2017-01-17 Thread shahar....@verint.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shahar Ron created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41138  
 
 
  Coverity - Job Failed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ken Dang  
 
 
Components: 
 coverity-plugin  
 
 
Created: 
 2017/Jan/17 3:38 PM  
 
 
Environment: 
 OS - Windows Server 2008R2 Datacenter  Jenkins - 2.32.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Shahar Ron  
 

  
 
 
 
 

 
 Using Coverity plugin to scan my *.py codes for the first time. Plugin was installed successfully and server configuration is valid. Once configured my first job to scan the code im getting the below output: Checking Coverity configuration... [Stream] CoverityPlatform/Kruvi/Kruvi_001 : OK (version: 8.6.0) [Node] Jenkins : version 8.6.0 Configuration is valid.  Building in workspace C:\Program Files (x86)\Jenkins\workspace\Hostname [C:\Program, Files\Coverity\Coverity, Static, Analysis\bin\cov-build, --dir, C:\Program, Files, (x86)\Jenkins\coverity\temp-241874536621283803.tmp, cmd, /c, call, C:\Windows\TEMP\hudson1372423268953757710.bat] [Hostname] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir $COV_IDIR cmd /c call C:\Windows\TEMP\hudson1372423268953757710.bat Coverity Build Capture (64-bit) version 8.6.0 on Windows Server 2008 R2 Server Datacenter (full installation), 64-bit, Service Pack 1 (build 7601) Internal version numbers: 2d06cace01 p-kent1-push-26368.885.208   C:\Program Files (x86)\Jenkins\workspace\Hostname>python -m compileall ./ C:\hostname\hostname.py  Listing ./ ...  C:\Program Files (x86)\Jenkins\workspace\Hostname>exit 0  [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:  C:/Program Files