Sorry about that - I quickly scanned my installed plugins and assumed
static analysis was responsible for generating the violations report. I
have installed:
Static Analysis Utilities
Checkstyle Plug-in
Jenkins Violations plugin
FindBugs Plug-in
PMD Plug-in
Warnings Plug-in
plus a bunch of others.
I have not tried downgrading the violations plugin yet - I was curious if
others were seeing the same behavior.
Thanks,
--Ryan
On Monday, 10 December 2012 16:02:15 UTC-5, Ullrich Hafner wrote:
>
> The violations plug-in is not part of the static analysis suite. Or are
> you referring to the analysis collector plug-in? You can try to downgrade
> the violations plug-in only. Does that help?
>
> Ulli
>
> Am 10.12.2012 um 21:37 schrieb Ryan Shoemaker
> >:
>
>
> > I updated Jenkins and all my plugins last week then created a new job
> that builds a new branch of our product. I noticed that the aggregated
> violations chart seems to be broken on the new job, but seems totally
> normal on the job that builds our main development branch.
> >
> > In order to get a violation delta between the main branch and new
> branch, I had the job first build the main branch to provide a baseline of
> the current violations. Then I reconfigured the job to build the new
> branch and it showed a nice delta between the two jobs (between builds 3 &
> 4) and the violations chart looked fine. A few hours later (even though
> there were no new builds of the job), the chart was empty as shown in the
> attachment. The individual charts for findbugs, pmd, and checkstyle all
> seem to be functioning properly though. Sometimes, the aggregated
> violations chart shows a single build ID on the x axis, sometimes not -
> even though I have the job configured to not discard any builds.
> >
> > If I click on the "checkstyle|pmd|findbugs warnings" links in the left
> column of the job page, they all seem to be working normally and the "New
> Warnings" column shows the correct count. However, if I click on the
> "violations" link in the left column of the job page, then I see an empty
> chart and it lists all of the mvn modules in my project and says "(didn't
> run)" next to each.
> >
> > I'm wondering if there's an issue with Jenkins or the static analysis
> plugin, or if my idea of switching branches to get a delta is somehow
> flawed (I'm pretty sure this has worked for me before).
> >
> > Anyone else seeing this? Should I downgrade my static analysis plugin?
> Anything else I can/should look for?
> >
> > Thanks,
> >
> > --Ryan
> >
>
>
