I believe that there is very little that you can do without the Coverity
Connect server.
I also looked at the Coverity plugin and decided that it was not going to help
too much. So instead I rolled my own using the imperative pipeline. What I do
is to pull back the results of a ‘canned’ view
Hello,
I am looking for help on run coverity through Jenkins as well. Not able to
find a post that helps me, just wonder whether you were able to get yours
working, and whether you would like to share some ideas on how to do it.
Thanks
Victoria
On Friday, September 14, 2012 7:31:35 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Coverity plugin
Hello,
I am looking for help on run coverity through Jenkins as well. Not able to
find a post that helps me, just wonder whether you were able to get yours
working, and whether you would like to share some ideas on how to do it.
Thanks
On Thu, Jun 12, 2014 at 10:33 AM, Ginga, Dick
dick.gi...@perkinelmer.com wrote:
I have run Coverity with Jenkins. The latest plugin is better than previous
ones but still not real robust.
We just do a batch/script that runs cov-build with the appropriate
command line options, then cov-analyze,
M also Facing the same problem. i am working on jenkin 1.483 version with
coverity plugin 1.1.3
[Coverity] No snapshot ID found in build log
Build step 'Coverity' changed build result to FAILURE
Build step 'Coverity' marked build as failure
Notifying upstream projects of job completion
Error is
Coverity Bug 41917 - Can't configure Jenkins plugin with Jenkins versions
1.463, 1.464, 1.465 has been fixed. The fix is available in version 1.1.3
of the Covertity Jenkins plugin. Here are the steps to install the plugin
in your Jenkins instance.
Manage Jenkins
Manage Plugins
Advanced
A Coverity support engineer used Jenkins 1.462 with no problem. If you
don't require Jenkins 1.463 or later, then 1.462 may be an acceptable
workaround.
Viktor - If you open a Coverity support case to be informed about the
Coverity bug, please direct the case to me. - Vaughn
On Friday, 11
I have the same issue and confirmed with the Coverity folks that they
too can recreate this bug. They have opened an internal bug to attempt
to resolve this issue. Coverity Bug #41917 for reference.
On May 11, 1:15 pm, Viktor Tarasov viktor.tara...@gmail.com wrote:
Hi,
I installed Coverity
