Daniel Beck commented on Bug JENKINS-16805

1) reloading from disk removed at least #40285 from the Jenkins UI. Why wouldn't it go away by itself without reloading the job configs?

My guess is that the build deletion got interrupted by some Windows process (e.g. your antivirus or search indexer) locking a file. Hence the build was still in memory, but no longer (in the expected location) on disk, so it could not be loaded again.

2) 2013-12-11_10-01-34 contains: changelog.xml, log file and timestamper directory which contains timestamps file

No build.xml file, so it cannot be loaded. You should see a warning logged about this on Jenkins startup.

3) when will those empty build directories being deleted from HDD which start with . as this job already has 13 of them?

To the best of my knowledge, when you delete them manually. Their existence means the deletion of a build failed.


That a failure to delete the dot-build directory causes Jenkins to keep the build in memory seems weird. Should probably be filed as a bug if it's not already.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to