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

Cannot configure # days for dashboard portlets.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: analysis-core-plugin
    • Labels:
      None
    • Environment:
      Hudson v 1.377 on Ubuntu.

      Description

      The analysis portlets ignore the number of # days you set.

      This affects all DashboardView portlets built on analysis-core.

      See attached screenshots for Checkstyle example.

        Activity

        Hide
        drulli Ulli Hafner added a comment -

        Can you please check if this also happens after refreshing the page with CTRL-F5? Does the size of the graph change if you modify the parameters?

        Show
        drulli Ulli Hafner added a comment - Can you please check if this also happens after refreshing the page with CTRL-F5? Does the size of the graph change if you modify the parameters?
        Hide
        drulli Ulli Hafner added a comment -

        And is this is a single project in the view or are there several ones?

        Show
        drulli Ulli Hafner added a comment - And is this is a single project in the view or are there several ones?
        Hide
        glundh glundh added a comment -

        Multiple projects. It is not a cache problem and is happening on all our Hudson clusters. The size parameters works fine.

        Show
        glundh glundh added a comment - Multiple projects. It is not a cache problem and is happening on all our Hudson clusters. The size parameters works fine.
        Hide
        glundh glundh added a comment -

        As you can see from the screenshots the priority distribution changes vastly but the New vs Fixed does not work at all. Similar issues on all various types of portlets. Also we have the latest versions installed of plugins and core components. The portlets have never worked for us (E.g. it is not a newly introduced issue).

        Show
        glundh glundh added a comment - As you can see from the screenshots the priority distribution changes vastly but the New vs Fixed does not work at all. Similar issues on all various types of portlets. Also we have the latest versions installed of plugins and core components. The portlets have never worked for us (E.g. it is not a newly introduced issue).
        Hide
        drulli Ulli Hafner added a comment -

        Integrated in Hudson Plug-ins (Compile) #75
        [FIXED JENKINS-8283] Use 'today' - 'jobTimestamp' when computing the builds that should be considered in a trend graph.

        Show
        drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #75 [FIXED JENKINS-8283] Use 'today' - 'jobTimestamp' when computing the builds that should be considered in a trend graph.
        Hide
        drulli Ulli Hafner added a comment -

        Since I changed the algorithm in several aspects I hope that now everything works fine. If possible, it would be nice if you can download the plugins from our build server and install them manually and test these before I make a public release: http://faktorzehn.org:8081/job/Hudson%20Plug-ins%20(Compile)/75/

        You need to install the analysis-core and the checkstyle plug-in.

        Show
        drulli Ulli Hafner added a comment - Since I changed the algorithm in several aspects I hope that now everything works fine. If possible, it would be nice if you can download the plugins from our build server and install them manually and test these before I make a public release: http://faktorzehn.org:8081/job/Hudson%20Plug-ins%20(Compile)/75/ You need to install the analysis-core and the checkstyle plug-in.
        Hide
        glundh glundh added a comment -

        Hi! Thanks for the prompt response. However, the result gets even stranger this time around. Please check the attached screenshot (CaptureFromSnapshotVersion.png).

        Show
        glundh glundh added a comment - Hi! Thanks for the prompt response. However, the result gets even stranger this time around. Please check the attached screenshot (CaptureFromSnapshotVersion.png).
        Hide
        drulli Ulli Hafner added a comment -

        Ok, I see. There are still builds considered that should be out of the specified range. Is the number of warnings in the left side correct?

        On the right side: do you have new or resolved warnings in the corresponding builds or is the increasing total number only because of adding new projects?

        Show
        drulli Ulli Hafner added a comment - Ok, I see. There are still builds considered that should be out of the specified range. Is the number of warnings in the left side correct? On the right side: do you have new or resolved warnings in the corresponding builds or is the increasing total number only because of adding new projects?
        Hide
        glundh glundh added a comment -

        The warnings are due to changes in the code being built. But please notice that the two graphs are not both the same type of warnings:

        • Checkstyle warnings
          and
        • Compiler warnings

        I wanted just to show that the two portlets renders the dates on the horizontal axis quite differently.

        More info: If I change to # 30 days, the same date range is being used, but more dates are being printed in the the time-axis. Really strange.

        Show
        glundh glundh added a comment - The warnings are due to changes in the code being built. But please notice that the two graphs are not both the same type of warnings: Checkstyle warnings and Compiler warnings I wanted just to show that the two portlets renders the dates on the horizontal axis quite differently. More info: If I change to # 30 days, the same date range is being used, but more dates are being printed in the the time-axis. Really strange.
        Hide
        drulli Ulli Hafner added a comment -

        Thanks again, I think I found the problem. My build time check is after the first value has been added That means that there are always some wrong values for projects that have no build result in the given period.

        Show
        drulli Ulli Hafner added a comment - Thanks again, I think I found the problem. My build time check is after the first value has been added That means that there are always some wrong values for projects that have no build result in the given period.
        Hide
        drulli Ulli Hafner added a comment -

        Do you have some jobs that have no result in the last 4 days?

        Show
        drulli Ulli Hafner added a comment - Do you have some jobs that have no result in the last 4 days?
        Hide
        glundh glundh added a comment -

        "Do you have some jobs that have no result in the last 4 days?"

        I'm not fully sure what you want me to verify here. The result is based on 50+ included projects and I'm pretty sure that quite a few of them does not have any result for the last 4 day.

        If you want me to try a specific setup, let me know.

        Show
        glundh glundh added a comment - "Do you have some jobs that have no result in the last 4 days?" I'm not fully sure what you want me to verify here. The result is based on 50+ included projects and I'm pretty sure that quite a few of them does not have any result for the last 4 day. If you want me to try a specific setup, let me know.
        Hide
        drulli Ulli Hafner added a comment -

        Integrated in Hudson Plug-ins (Compile) #77
        [FIXED JENKINS-8283] Check the build times before adding the first result (since a project might not have any builds in the defined range).

        Show
        drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #77 [FIXED JENKINS-8283] Check the build times before adding the first result (since a project might not have any builds in the defined range).
        Hide
        drulli Ulli Hafner added a comment -

        I think I finally fixed it now

        One drawback of the fix: if a project has no builds in the selected range, then there a no warnings counted. Maybe I should change that and reuse the last available result for that build, and use that result for all the visible days (as this is done for builds that have no result on a specific day). What do you think?

        Show
        drulli Ulli Hafner added a comment - I think I finally fixed it now One drawback of the fix: if a project has no builds in the selected range, then there a no warnings counted. Maybe I should change that and reuse the last available result for that build, and use that result for all the visible days (as this is done for builds that have no result on a specific day). What do you think?
        Hide
        glundh glundh added a comment -

        Reuse the last results sounds fine to me.

        And again, thanks for the quick response and fix

        Show
        glundh glundh added a comment - Reuse the last results sounds fine to me. And again, thanks for the quick response and fix
        Hide
        glundh glundh added a comment -

        And the new version is now tested and seems to work fine. Time for a new release?

        Show
        glundh glundh added a comment - And the new version is now tested and seems to work fine. Time for a new release?
        Hide
        drulli Ulli Hafner added a comment -

        I'm waiting for a pending change in the findbugs plugin. Hopefully, there will be a christmas release

        Show
        drulli Ulli Hafner added a comment - I'm waiting for a pending change in the findbugs plugin. Hopefully, there will be a christmas release

          People

          • Assignee:
            drulli Ulli Hafner
            Reporter:
            glundh glundh
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: