Hi,
That sounds like you are either archiving the results of each build or
do generate fingerprints of the artifacts...fingerprints are only needed
if you try to make dependencies between jobs with SNAPSHOT's otherwise
is useless.
Furthermore are you using a local maven cache (ake local repository) for
each job?
Kind regards
Karl Heinz Marbaise
On 5/25/16 11:21 AM, Jorg Heymans wrote:
Hi,
I reported this a couple of months ago, is anyone else seeing this ?
https://issues.jenkins-ci.org/browse/JENKINS-34233
Several times already we have noticed that the build time of certain of
our maven jobs increases substantially over the course of several
months. We are talking from 30s initially to 3-4 minutes after six
months. This happens for jobs configured to run on our solaris build
server , but also jobs configured to run on windows slaves.
It is easy to tell a job is getting slow because during maven init it
takes a long time to get passed "Scanning for projects" :
13:06:54 [INFO] Scanning for projects...
13:08:03 [INFO]
------------------------------------------------------------------------
As you can see more than 70 seconds during maven init is not normal.
We found out that when we recreate the job (basically just a copy of the
job under a different name from the UI, then delete the slow one and
rename the copy to the original) performance is back to normal. But
after a few months the slowdown becomes noticeable again.
Any thoughts as to what could be causing this ?
Jorg
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/920c88b1-3d91-de4d-5064-b17179dae0c2%40gmx.de.
For more options, visit https://groups.google.com/d/optout.
