Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16457

Bogus Jenkins.rawBuildsDir not adequately diagnosed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      If you set Jenkins.rawBuildsDir to an inappropriate value, such as /nonexistent (a path you cannot even create), Jenkins:

      1. Does not warn you in the configuration screen.
      2. Fails to create new build records. These are reported as a series of exceptions from Run.execute with adequate diagnostics, but not very gracefully.
      3. Silently fails to load build records after a restart. Fixed earlier as: https://github.com/jenkinsci/jenkins/commit/a516ade0fe668fb37443206a14381d7efcf0b83b
      4. 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.)

        Attachments

          Issue Links

            Activity

            jglick Jesse Glick created issue -
            scm_issue_link SCM/JIRA link daemon made changes -
            Field Original Value New Value
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-17138 [ JENKINS-17138 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 147279 ] JNJira + In-Review [ 192316 ]

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              jglick Jesse Glick
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: