Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28360

Missing static analysis results in weather popup

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Cannot Reproduce

    Description

      I recently updated our Jenkins server from 1.565.2 to 1.596.2. As part of that, a lot of plugins that were fine had to be updated, to squelch various DEPRECATED warnings in the log file (and some things that just plain broke). Unfortunately, while updating the plugins I lost the thing that showed the results of our static analysis checking in the on-mouseover hover of "weather" on the main dashboard.

      This is a bit of a shot in the dark, but the plugins listed in "Environment" were the only ones that were related to static analysis checking in our deployment, so I'm hoping you know how to get that back. The developers apparently use it to quickly check on all the various projects, and having to click through to each one is burdensome.

      Attached is a screenshot of what we see now. Previously, "Static Checking" was another row in that popup.

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          Hmm, actually there should be also a line for each plug-in in the health report (when the health configuration is defined as you have shown above). Strange that these results are not shown, but the collector result is shown...

          drulli Ulli Hafner added a comment - Hmm, actually there should be also a line for each plug-in in the health report (when the health configuration is defined as you have shown above). Strange that these results are not shown, but the collector result is shown...
          teancom David Bishop added a comment -

          Ah! Well, my developers are now asking me for the broken-out results to show in the health report as well, so if you have any ideas as to somewhere else I can look I'm all ears.

          teancom David Bishop added a comment - Ah! Well, my developers are now asking me for the broken-out results to show in the health report as well, so if you have any ideas as to somewhere else I can look I'm all ears.
          drulli Ulli Hafner added a comment -

          Works in my test setup (1.611) without any problems. I'll add an acceptance test and see if it behaves differently when used with 1.596.2.

          drulli Ulli Hafner added a comment - Works in my test setup (1.611) without any problems. I'll add an acceptance test and see if it behaves differently when used with 1.596.2.

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorFreestyleBuildSettings.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorSettings.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisSettings.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/checkstyle/CheckStyleAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/findbugs/FindBugsAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/pmd/PmdAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/tasks/TaskScannerAction.java
          src/main/java/org/jenkinsci/test/acceptance/plugins/warnings/WarningsAction.java
          src/test/java/plugins/AbstractAnalysisTest.java
          src/test/java/plugins/AnalysisCollectorPluginTest.java
          http://jenkins-ci.org/commit/acceptance-test-harness/b9c687643cc774c6e82de20662fff9b0236c2d82
          Log:
          JENKINS-28360 Added a test case to verify the health reports.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorFreestyleBuildSettings.java src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorSettings.java src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisSettings.java src/main/java/org/jenkinsci/test/acceptance/plugins/checkstyle/CheckStyleAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/findbugs/FindBugsAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/pmd/PmdAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/tasks/TaskScannerAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/warnings/WarningsAction.java src/test/java/plugins/AbstractAnalysisTest.java src/test/java/plugins/AnalysisCollectorPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/b9c687643cc774c6e82de20662fff9b0236c2d82 Log: JENKINS-28360 Added a test case to verify the health reports.
          drulli Ulli Hafner added a comment -

          Is this still a problem in your environment? I just started the new acceptance tests with Jenkins 1.592.2 without any failures.

          drulli Ulli Hafner added a comment - Is this still a problem in your environment? I just started the new acceptance tests with Jenkins 1.592.2 without any failures.

          People

            drulli Ulli Hafner
            teancom David Bishop
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: