-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
Overnight, for the last two nights, the symlinks to all the lastXBuilds have broken – apparently spontaneously (without any builds taking place).
They now refer to:
jenkins@gsbuild:~/jobs/Gulfstream-build-vm/builds$ ls -la lrwxrwxrwx 1 jenkins nogroup 19 May 24 16:14 1 -> 2013-05-24_16-14-27 drwxr-xr-x 3 jenkins nogroup 4096 May 24 16:14 2013-05-24_16-14-27 ... lrwxrwxrwx 1 jenkins nogroup 2 May 30 09:12 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins nogroup 2 May 30 09:12 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins nogroup 2 May 30 09:12 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins nogroup 2 May 24 16:14 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins nogroup 2 May 30 09:12 lastUnsuccessfulBuild -> -1
Although note that the actual job directories are still present, along with their job number links.
Additionally, in the web UI, the build history is now empty.
Starting a new job causes the build history to be populated correctly, and the symlinks to be updated appropriately.
Expected behaviour is for the symlinks to always work, and for the history UI to always be populated with the last few jobs.
I've attached my log file, in case that's useful.
- is related to
-
JENKINS-18168 Jenkins "loosing" builds
-
- Resolved
-