Sudden increase in build times of Maven-style job

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Sudden increase in build times of Maven-style job

Somya

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/50969dc8-7225-4c41-8c3a-ca78cb799c50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Sudden increase in build times of Maven-style job

Mukarram Baig
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a2f6e03c-3a5f-4ec2-b120-491dcc101f80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Sudden increase in build times of Maven-style job

Mukarram Baig
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b24dde8a-3385-4c41-8305-987ffd2aa6a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Sudden increase in build times of Maven-style job

Raghuram Duraisamy
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 [hidden email].
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.
R
Reply | Threaded
Open this post in threaded view
|

Re: Sudden increase in build times of Maven-style job

R
In reply to this post by Somya
Hi  All,
Facing same issue, did any of you were able to identify root cause or any other workaround.

Also, as per analysis of our maven job logs, we could see , Step "Writing OBR metadata" under "maven-bundle-plugin:install (default-install) " per module time has been increased. Though unable to identify root cause or resolution to bring it back to normal state.

If any of you have any idea regarding this, please let me know.

Thank You.

On Monday, June 8, 2015 at 7:22:32 PM UTC+5:30, 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4f6193b7-f5a5-4f7b-be18-1d51ca487777%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.