I removed the include pattern "jobs/*/promotions/*/config.xml", now the
fingerprinting takes no time :D.
I think I can conclude that the scan pattern really slows things down
when there are many jobs.
Something interesting is, the scandir is triggered by
FingerPrint.save(), SCM sync config plu
The SCM sync configuration:
Am 11.07.2013 17:10, schrieb John Vacz:
Executor #1 for Slave16 : executing SD-2112 #3
"Executor #1 for comitdev16 : executing SD-2112 #3" Id=62 Group=main RUNNABLE
at java.io.UnixFileSystem.list(Native Method)
at java.io.File.list(File.java:97
Executor #1 for Slave16 : executing SD-2112 #3
"Executor #1 for comitdev16 : executing SD-2112 #3" Id=62 Group=main RUNNABLE
at java.io.UnixFileSystem.list(Native Method)
at java.io.File.list(File.java:973)
at
org.apache.tools.ant.DirectoryScanner.scandir(DirectorySca
The artifacts:
30MB x 1,
6.5MB x 9,
1MB x 1,
others are 5 plain text files between 0.1 ~ 10KB.
I will look into the threadDump...
Am 11.07.2013 16:33, schrieb Daniel Beck:
How big are these artifacts?
At /threadDump, you can access live stack traces. Maybe look for something
fingerprint rela
How big are these artifacts?
At /threadDump, you can access live stack traces. Maybe look for something
fingerprint related during those 5 minutes, it could give you a hint what is
taking so long.
Copy artifact works without fingerprinting in the source project, but always
calculates its own w
Recently the fingerprinting of our jubs is becoming very slow.Per build
we have 16 artifacts to be fingerprinted, now that alone lasts ~5
minutes. Since we are using copy artifact plugin very heavily, the
situation is becoming even worse - the slowness adds up.
Unfortunately I cannot tell from
