Skip to content

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

Closed
Closed
[JENKINS-8754] ROADMAP: Improve Start-up Time#15615
Labels
component:coreenhancementimported-jira-issuepriority:majorresolution:duplicate

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on Feb 10, 2011

Original discussion: https://groups.google.com/d/topic/jenkinsci-dev/_cuKEAUULUE/discussion

> - Startup time

Originally reported by jieryn, imported from: ROADMAP: Improve Start-up Time
  • assignee: kohsuke
  • status: Closed
  • priority: Major
  • component(s): core
  • resolution: Duplicate
  • resolved: 2012-10-12T12:50:02+00:00
  • votes: 39
  • watchers: 35
  • imported: 2025-11-24
Raw content of original issue 
Original discussion: https://groups.google.com/d/topic/jenkinsci-dev/_cuKEAUULUE/discussion



> - Startup time

Activity

  1. jenkins-infra-bot commented on Mar 7, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Mar 7, 2011
    Author
    jieryn:
    • Original comment link
    • Raw content of original comment: 
      Does Jenkins really need to parse the job log for all previous jobs before it is ready to do work?

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

  2. jenkins-infra-bot commented on Mar 8, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Mar 8, 2011
    Author
    neu242:

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

  3. jenkins-infra-bot commented on Mar 13, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Mar 13, 2011
    Author
    morlajb:
    • Original comment link
    • Raw content of original comment: 
      Do you time estimation for this one ??

    Do you time estimation for this one ??

  4. jenkins-infra-bot commented on Oct 10, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 10, 2012
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment: 
      I'm marking this resolved based on the fix in 1.485 that does lazy loading of build records.

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

  5. jenkins-infra-bot commented on Oct 11, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 11, 2012
    Author
    jburrows:
    • Original comment link
    • Raw content of original comment: 
      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.

    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.

  6. jenkins-infra-bot commented on Oct 12, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 12, 2012
    Author
    jburrows:
    • Original comment link
    • Raw content of original 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)

    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: 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: 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: 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)

  7. jenkins-infra-bot commented on Oct 12, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 12, 2012
    Author
    oldelvet:

    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/

  8. jenkins-infra-bot commented on Oct 12, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 12, 2012
    Author
    jburrows:
    • Original comment link
    • Raw content of original comment: 
      More info, after each restart of Jenkins, it clears out any and all build history again.

    More info, after each restart of Jenkins, it clears out any and all build history again.

  9. jenkins-infra-bot commented on Oct 12, 2012

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 12, 2012
    Author
    jburrows:

    Looks like the issue was re-opened as another issue:
    See JENKINS-15465 and JENKINS-15439

  10. jenkins-infra-bot
    closed this as completedon Oct 12, 2012

  11. jenkins-infra-bot commented on Jan 22, 2013

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jan 22, 2013
    Author
    nickolay_martinov:

    Looks like this feature breaks a lot. See https://issues.jenkins-ci.org/browse/JENKINS-15156
    Would be nice to have a patch that reverts the change.

  12. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15156]

  13. jenkins-infra-bot
    added
    imported-jira-issue
    component:core
    enhancement
    on Nov 24, 2025

  14. 7 remaining items

  15. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15560]

  16. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15587]

  17. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-16845]

  18. jenkins-infra-bot
    added
    resolution:duplicate
    on Nov 24, 2025

  19. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-17265]

  20. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-18065]

  21. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15333]

  22. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15533]

  23. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15583]

  24. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15589]

  25. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-16023]

  26. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15594]

  27. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-15929]

  28. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-18289]

  29. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original depends_on from Jira: JENKINS-16089]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:coreenhancementimported-jira-issuepriority:majorresolution:duplicate

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions