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.)
SCM/JIRA link daemon made changes -
|Field||Original Value||New Value|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
R. Tyler Croy made changes -
|Workflow||JNJira [ 147279 ]||JNJira + In-Review [ 192316 ]|