Hi,

I am trying to pinpoint a performance issue we are incurring with maven
under Jenkins. Basically what we are seeing is that maven is taking a very
long time getting past the initial 'Scanning for projects' message. As you
can see in below snippet, more than half a minute elapses before the first
module is starting to build.

*00:00:11.634* Maven home:
/home/ci/jenkins/data/tools/hudson.tasks.Maven_MavenInstallation/maven3*00:00:11.634*
Java version: 1.7.0_80, vendor: Oracle Corporation*00:00:11.634* Java
home: /home/ci/jenkins/data/tools/hudson.model.JDK/jdk1.7/jre*00:00:11.634*
Default locale: en, platform encoding: ISO646-US*00:00:11.634* OS
name: "sunos", version: "5.10", arch: "sparc", family: "unix"

*00:00:11.757* [INFO] Scanning for projects...

*00:00:42.350* [INFO]
                       *00:00:42.350* [INFO]
------------------------------------------------------------------------*00:00:42.350*
[INFO] Building Document Implementation 0.2-SNAPSHOT


This is a very small project we're building, containing only one maven
module. In this case it's half a minute, we have seen other maven
builds where it takes 2-3 minutes or more.


Can anyone tell me what maven is doing in this 'Scanning for projects'
that is potentially very slow ? If i run the build in offline mode the
problem disappears, but that is not an option for us. Note that
developers executing builds locally do not see the same performance
issue.


Thanks,

Jorg


PS the thread on the jenkins forum
https://groups.google.com/forum/#!topic/jenkinsci-users/3s2MeImr2eY

Reply via email to