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

Add "process last N builds for trend" to "Configure System" Jenkns page.

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • performance-plugin
    • None
    • Performance Plugin 1.7

      Generating trend graphs in case there are hundreds of builds is very resource intensive task. Currently there is an option for setting this limit in browser cookie (btw I have just filled issue - it doesn't work) but before user set it to explicit value, all available builds are taken into consideration. This can be very bad and block Jenkins from responding because it's crazy busy parsing gigs of data.
      Cookie has also important disadventage: can expire, be cleared and is attached to one browser. If user logs in from another location limit setting is lost.

      My proposition is to add this limit to Jenkins "Configure System" page just like it's done for many popular plugins.

      Cheers!

        1. Screenshot (8).png
          Screenshot (8).png
          79 kB

          [JENKINS-13372] Add "process last N builds for trend" to "Configure System" Jenkns page.

          Craig de Stigter added a comment -

          +1 In addition to performance improvements, this would really make trend graphs much more useful, since it's hard to get any meaningful information from a graph that looks like this: http://i.imgur.com/HUz9FKi.png

          Craig de Stigter added a comment - +1 In addition to performance improvements, this would really make trend graphs much more useful, since it's hard to get any meaningful information from a graph that looks like this: http://i.imgur.com/HUz9FKi.png

          Philippe Mouawad added a comment -

          undera, artem_fedorov this enhancement looks interesting to me.

          IMO, the best place for this should be per project not as global settings.

          I see few options:

          • Either we persist what is currently saved as cookie in Configure the trend graph, but this screen is not immediately visible
          • Either we add an option 'Number of builds to consider' on same level as Source data files
          • Other proposals ?

          Thanks for feedback.

          Philippe Mouawad added a comment - undera , artem_fedorov this enhancement looks interesting to me. IMO, the best place for this should be per project not as global settings. I see few options: Either we persist what is currently saved as cookie in Configure the trend graph, but this screen is not immediately visible Either we add an option 'Number of builds to consider' on same level as Source data files Other proposals ? Thanks for feedback.

          Artem Fedorov added a comment -

          Hi pmouawad
          Performance Trend already has filter for configure the trend graph for each job

          Artem Fedorov added a comment - Hi pmouawad Performance Trend already has filter for configure the trend graph for each job

          Philippe Mouawad added a comment -

          Hi artem_fedorov,

          Yes I am aware of it, but it relies on Cookie of user.

          The proposal here is to configure it persistently and accross all users.

           

          Regards

          Philippe Mouawad added a comment - Hi artem_fedorov , Yes I am aware of it, but it relies on Cookie of user. The proposal here is to configure it persistently and accross all users.   Regards

            pmouawad Philippe Mouawad
            zimnyx Piotr Czachur
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: