Jenkins maintainers, I am facing this exact issue. Would appreciate any help extended in identifying or resolving the problem :)
Thanks, Raghuram On Thursday, July 2, 2015 at 10:32:34 PM UTC+5:30, Mukarram Baig wrote: > > Hello guys, > > Is there any logging that will help us get to the bottom of the problem > here? > > > > On Thursday, 18 June 2015 12:37:27 UTC-4, Mukarram Baig wrote: >> >> I am also seeing the same behavior and renaming the build job brought the >> time back into a reasonable range. Is there any logging that can be turned >> on so that we can get some clues on the culprit? >> >> Thanks! >> >> On Monday, 8 June 2015 09:52:32 UTC-4, Somya wrote: >>> >>> Hi, >>> >>> >>> >>> I have a Maven build job setup in Jenkins, with following notable >>> configs : >>> >>> >>> >>> · It is a multi-module job with 75 modules >>> >>> · It is built incrementally (build only changed modules) >>> >>> · Automatic artifact archiving is disabled >>> >>> · “Resolve Dependencies during Pom parsing” and “Process >>> Plugins during Pom parsing” are disabled. >>> >>> >>> >>> The build time is approx *20 mins*. However, from some time the build >>> time has* drastically increased to 1 hr 15 mins*. The current build >>> number is about *1450 *and I am preserving only *3 old builds*. My >>> question is why there is such high increment in build times suddenly? >>> >>> >>> >>> The things I have tried and observed so far : >>> >>> >>> >>> · The timestamping of build output shows that major time is >>> being spent in "*Parsing POMs*" (approx 30 mins) and "*Metadata >>> collection*" step (approx 20 mins). >>> >>> · A full build, instead of an incremental build, also takes >>> about 1 hr 20 mins. >>> >>> · I cleaned up all the existing fingerprints data and tried >>> rebuilding the project. This had no impact on the build time. >>> >>> · I also tried building the job on a dedicated slave, in case >>> the problem was due to resource availability. This had no impact on build >>> times. >>> >>> >>> >>> The only thing that worked was renaming the job itself. After renaming >>> build are completing again in approx 20 mins. But I am not sure if this is >>> an ideal solution. Also I don't understand the reason behind this approach >>> of renaming the job. Does anyone have an idea as to why the build times >>> increased and how to fix this ? >>> >>> >>> I am using *Jenkins v1.560* and *maven project plugin v2.0.* Upgrading >>> Maven plugin or Jenkins is not an option for me now. >>> >>> >>> >>> Thanks, >>> >>> Somya >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/96081cb9-b05c-47e5-b46f-801a9f1824c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
