JenkinsIcon indicating the project type

Jenkins

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

Page load time of inheritance projects

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: project-inheritance-plugin
    • Labels:
      None
    • Environment:
      Windows 7 64-bit, Mozilla Firefox browser
    • Similar Issues:

      Description

      The page load time for any inheritance-plugin-based project is much longer than for a traditional Jenkins project. Please improve this in future versions.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          smb Steffen Buehl added a comment -

          can confirm this issue with 1.5.3. page load times are > 2 seconds - nothing unusual in the logfile.

          after downgrading to 1.5.1 the loading times were fine again.

          Show
          smb Steffen Buehl added a comment - can confirm this issue with 1.5.3. page load times are > 2 seconds - nothing unusual in the logfile. after downgrading to 1.5.1 the loading times were fine again.
          Hide
          Permalink
          escoem Emilio Escobar added a comment -

          It seems that the plugin is evaluating all the parameters from all the inheritance-project jobs at the current view (and build history too).

          Show
          escoem Emilio Escobar added a comment - It seems that the plugin is evaluating all the parameters from all the inheritance-project jobs at the current view (and build history too).
          Hide
          Permalink
          escoem Emilio Escobar added a comment -

          Hi Martin Schröder, after 1.5.3 with the add of copyAndSortParametersByName instead of sortParametersByName we are facing performance issues. Basically because every parameters inside inheritance jobs are evaluated every time a dashboard is rendered, or build history is rendered. Also there is a trigger? thats evaluate continuously thous parameters. This is really needed? It seems that there is a lack of performance here. Thanks!

          Show
          escoem Emilio Escobar added a comment - Hi Martin Schröder , after 1.5.3 with the add of copyAndSortParametersByName instead of sortParametersByName we are facing performance issues. Basically because every parameters inside inheritance jobs are evaluated every time a dashboard is rendered, or build history is rendered. Also there is a trigger? thats evaluate continuously thous parameters. This is really needed? It seems that there is a lack of performance here. Thanks!

            People

            • Assignee:
              Unassigned
              Reporter:
              ajthomas Arun Thomas
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: