FWIW i also tested with an empty maven repository, no difference. So it
must be something that is happening when it parses the POM for dependencies
?
On Wednesday, June 1, 2016 at 10:45:28 AM UTC+2, Jorg Heymans wrote:
>
> The maven repository used is one local to the executor. It is not
>
The maven repository used is one local to the executor. It is not
particularly huge. Note that developers executing builds locally of the
same module do not see this problem.
Doing a threaddump at the moment where it is scanning for projects revealed
nothing special:
Channel reader thread:
Is there a workspace-private local Maven repository? Maybe repository
operations (up to date check?) take long…
I think for Maven jobs, you should be able to see internal state (current
threads' stacks?) in the Jenkins UI.
> On 30.05.2016, at 10:14, Jorg Heymans wrote:
Interestingly, executing offline with -o makes the problem disappear. But
this is obviously not a solution for me..
Jorg
On Monday, May 30, 2016 at 9:52:04 AM UTC+2, Jorg Heymans wrote:
>
> Sadly there is no additional debug output being emitted during the
> 'scanning for projects' phase, with
Sadly there is no additional debug output being emitted during the
'scanning for projects' phase, with -X set.
*00:00:10.329* [DEBUG] Reading user settings from
C:\.m2\settings.xml*00:00:10.378* [INFO] Scanning for projects...*00:00:56.941*
[INFO]
Good point! Trying this and will report back ...
--
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
Jorg Heymans
writes:
> 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]
>
Hi,
We have a local maven repo per executor. We do not archive any artifacts. I
have not configured anything specifically for fingerprinting so whatever is
the default is currently active.
As i said the slowdown occurs during maven init, when it says 'Scanning for
projects' , has Jenkins
No, we keep only two builds. And we do not even archive any artifacts, just
a simple clean install.
Jorg
On Wednesday, May 25, 2016 at 3:39:32 PM UTC+2, David Karlsen wrote:
>
> Are you keeping a lot of build history?
> 25. mai 2016 11:21 skrev "Jorg Heymans" >:
>
>>
Are you keeping a lot of build history?
25. mai 2016 11:21 skrev "Jorg Heymans" :
> 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
10 matches
Mail list logo