When we have the symbolic links in src code like,
dir1 -> .
dir2 -> ../../../..
Symptoms observed during this problematic phase:
- The “Archiving artifact” step under Post- build phase get stuck. We can see the never ending cycling icon…
- the slave node will report error like “too many levels of symbolic links” and ping response time would gradually degrade, eventually killing the slave.
- the build log may also have error like WARN: Caught error while checking for symbolic links
- is related to
-
JENKINS-36559 File pattern (e.g. archive) field validation can run forever
- Open
-
JENKINS-40999 Recursive symlink causes high resource utilization, termination of slave process in ArchiveArtifact and Publish JUnit results steps.
- Open
-
JENKINS-41135 java.lang.OutOfMemoryError: Java heap space with 100% CPU usage
- Resolved