Jenkins should fail initialization if it can not parse a job history

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: core
    • Environment:
      Linux/tomcat - Jenkins version 1.436

      If the file

      configuration/jobs/<job>/nextBuildNumber

      is empty, Jenkins will still initialize but the job will "disappear" from the dashboard. This will be logged, but may go unnoticed.

      Oct 27, 2011 3:10:24 PM jenkins.model.Jenkins$6 onTaskFailed
      SEVERE: Failed Loading job accurev_trigger
      hudson.util.IOException2: <path>/configuration/jobs/<job>/nextBuildNumber doesn't contain a number

            Assignee:
            Unassigned
            Reporter:
            pickgr
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: