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

Cache estimated duration for execution

    XMLWordPrintable

Details

    Attachments

      Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. JENKINS-48821 Time remaining for all pipeline jobs is N/A

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Resolved
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. JENKINS-50030 Job.getEstimatedDurationCandidates should not force loading of builds

        • Major - Major loss of function.
        • Open

        Activity

          Descending order - Click to sort in ascending order
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Alexander Akbashev
          Path:
          core/src/main/java/hudson/model/Executor.java
          http://jenkins-ci.org/commit/jenkins/e0ea7a648ed6970897ea2c49bc662439ec4e4110
          Log:
          JENKINS-48350 Cache estimated duration for execution

          In case of having 1000s of ongoing builds opening main pages can take
          some time if list of executors are opened. It happens because for every
          queury that comes from jelly we re-calculate the value from scratch. And
          calculation needs to load some builds from disk. The worst thing is that it
          happens for every user separately.

          (cherry picked from commit d7b120fea37b46b863c89acb638d04cdddc868b4)

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alexander Akbashev Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/e0ea7a648ed6970897ea2c49bc662439ec4e4110 Log: JENKINS-48350 Cache estimated duration for execution In case of having 1000s of ongoing builds opening main pages can take some time if list of executors are opened. It happens because for every queury that comes from jelly we re-calculate the value from scratch. And calculation needs to load some builds from disk. The worst thing is that it happens for every user separately. (cherry picked from commit d7b120fea37b46b863c89acb638d04cdddc868b4)
          oleg_nenashev Oleg Nenashev added a comment -

          It has been released in 2.92.
          jimilian in order to mark is as LTS candidate, the changelog on jenkins.io needs to be updated

          oleg_nenashev Oleg Nenashev added a comment - It has been released in 2.92. jimilian in order to mark is as LTS candidate, the changelog on jenkins.io needs to be updated

          People

            oleg_nenashev Oleg Nenashev
            jimilian Alexander A
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: