-
Bug
-
Resolution: Fixed
-
Minor
-
None
If you set Jenkins.rawBuildsDir to an inappropriate value, such as /nonexistent (a path you cannot even create), Jenkins:
- Does not warn you in the configuration screen.
- Fails to create new build records. These are reported as a series of exceptions from Run.execute with adequate diagnostics, but not very gracefully.
- Silently fails to load build records after a restart. Fixed earlier as: https://github.com/jenkinsci/jenkins/commit/a516ade0fe668fb37443206a14381d7efcf0b83b
- Silently shows an empty console, missing changelog, etc. when displaying the build later. (Unlike #2/#3, there is no diagnostic if you have changed the build root within a Jenkins session after running a build.)
- is related to
-
JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds
-
- Resolved
-
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/Run.java
core/src/main/java/hudson/model/listeners/RunListener.java
core/src/main/java/jenkins/model/Jenkins.java
http://jenkins-ci.org/commit/jenkins/4ef6a6431990ae36d4e7dc376b3f0be9b1ee2625
Log:
[FIXED JENKINS-16457] Bogus Jenkins.rawBuildsDir not adequately diagnosed.