• Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

          [JENKINS-8754] ROADMAP: Improve Start-up Time

          jieryn created issue -

          jieryn added a comment -

          Does Jenkins really need to parse the job log for all previous jobs before it is ready to do work?

          jieryn added a comment - Does Jenkins really need to parse the job log for all previous jobs before it is ready to do work?

          neu242 added a comment -

          neu242 added a comment - Also discussed here: https://groups.google.com/group/jenkinsci-users/browse_thread/thread/2d49153524aae172#

          morlajb added a comment -

          Do you time estimation for this one ??

          morlajb added a comment - Do you time estimation for this one ??

          I'm marking this resolved based on the fix in 1.485 that does lazy loading of build records.

          Kohsuke Kawaguchi added a comment - I'm marking this resolved based on the fix in 1.485 that does lazy loading of build records.
          Kohsuke Kawaguchi made changes -
          Assignee New: Kohsuke Kawaguchi [ kohsuke ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          John Burrows added a comment - - edited

          So, how do we get the build records to load now? Sure, it starts faster, but now it does not show any build records for any of the builds prior to the update. v1.485, if you get rid of prior build records and start fresh, then maybe it would have been nice to state that in the change log.

          John Burrows added a comment - - edited So, how do we get the build records to load now? Sure, it starts faster, but now it does not show any build records for any of the builds prior to the update. v1.485, if you get rid of prior build records and start fresh, then maybe it would have been nice to state that in the change log.

          John Burrows added a comment -

          Build records are not getting loaded at all, even after the Jenkins service has been up for more than 18 hours. If there is some step needed to get back the build records or get them loaded, it should have been represented in the Changelog.
          Please fix this issue.
          Log entries show:

          I looked at the 'jenkins.err' on the Jenkins server & saw errors similar to these:

          Oct 12, 2012 2:06:01 AM org.kohsuke.stapler.compression.CompressionFilter reportException
          WARNING: Untrapped servlet exception
          javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/hudson/model/View/index.jelly:44:43: <st:include> org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/hudson/projectView.jelly:60:22: <d:invokeBody> org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/layout/tab.jelly:46:18: <j:otherwise> Failed to write to client
          at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
          at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
          at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
          at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
          at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625)
          at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
          at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
          at org.kohsuke.stapler.Stapler.service(Stapler.java:162)

          Oct 12, 2012 2:11:01 AM hudson.model.Run execute
          INFO: DBS_RETAIL_R5-SNAPSHOT #102 main build action completed: SUCCESS
          Oct 12, 2012 2:11:01 AM hudson.model.Executor run
          SEVERE: Executor threw an exception
          java.lang.NullPointerException
          at hudson.tasks.LogRotator.perform(LogRotator.java:119)
          at hudson.model.Job.logRotate(Job.java:338)
          at hudson.model.Run.execute(Run.java:1581)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:236)

          John Burrows added a comment - Build records are not getting loaded at all, even after the Jenkins service has been up for more than 18 hours. If there is some step needed to get back the build records or get them loaded, it should have been represented in the Changelog. Please fix this issue. Log entries show: I looked at the 'jenkins.err' on the Jenkins server & saw errors similar to these: Oct 12, 2012 2:06:01 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/hudson/model/View/index.jelly:44:43: <st:include> org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/hudson/projectView.jelly:60:22: <d:invokeBody> org.apache.commons.jelly.JellyTagException: jar: file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/layout/tab.jelly:46:18: <j:otherwise> Failed to write to client at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) Oct 12, 2012 2:11:01 AM hudson.model.Run execute INFO: DBS_RETAIL_R5-SNAPSHOT #102 main build action completed: SUCCESS Oct 12, 2012 2:11:01 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.tasks.LogRotator.perform(LogRotator.java:119) at hudson.model.Job.logRotate(Job.java:338) at hudson.model.Run.execute(Run.java:1581) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)
          John Burrows made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439. I'm pretty sure that those are the issues that you are seeing.

          Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from
          https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/

          Richard Mortimer added a comment - There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439 . I'm pretty sure that those are the issues that you are seeing. Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/

            kohsuke Kohsuke Kawaguchi
            jieryn jieryn
            Votes:
            39 Vote for this issue
            Watchers:
            35 Start watching this issue

              Created:
              Updated:
              Resolved: