there is certainly a way of gathering the total "fixed" issues at any point in time. then you save each of those and graph that set. My perl program however resides on my previous employers computer. I might have used the Perl module GD::Graph for the graphing. and I was able to display it in Jenkins under a view description by using an aref html statement.
And we don't use Coverity here now. As I recall, examples are helpful but some learning will be required. On Thu, Mar 16, 2017 at 12:56 PM, Pradeep Patra <[email protected]> wrote: > Yes, We could able to collect the coverity data fort each module > connecting to coverity-connecting server through GUI. Actually when the > time passes we may fix some issues and the fixing trend is more important > as part of quality metrics. So I was thinking is there a way to achieve > this ? > > Does your perl module get coverity data and displays the fixing trend > through graph? > > On Thursday, March 16, 2017 at 6:07:19 PM UTC+5:30, Richard Ginga wrote: >> >> Pradeep, unless there is something new in the coverity plugin, the answer >> is no or, more accurately, I don't know of one. The Coverity plugin will >> display historic # of defects discovered. What you want, i'm sure you know, >> is available on the your Coverity-Connect server. >> >> there is a Coverity Perl module that I have used to gather such >> information. >> >> On Thu, Mar 16, 2017 at 12:18 AM, Bubunia Patra <[email protected]> >> wrote: >> >>> Hi, >>> >>> I was curious to know whether we have a opensource Jenkins plugin to >>> show the coverity trend to show the fixing trend in graphs and charts ? >>> >>> Regards >>> Pradeep >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/jenkinsci-users/0fd8fe38-90eb-4241-9865-3329af96b277% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/0fd8fe38-90eb-4241-9865-3329af96b277%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Dick Ginga >> Build Engineer >> [email protected] >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/3fd7972d-d0e3-4ee0-a2a4-6e07d08aa2fa%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/3fd7972d-d0e3-4ee0-a2a4-6e07d08aa2fa%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Dick Ginga Build Engineer [email protected] -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaWxjKcXbfz%3DyCEiYHn1HAtfjz1X9rDi9pkm6T-2i2JJ2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
