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

Reloading configuration leads to lost build status

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • Linux, Ubuntu 9.04

      When reloading the Hudson configuration from disk the status of some builds is lost. These builds only show the first build ever run for the job.

      So far I have been unable to determine which job parameters lead to loss of status after reload.

      The standard jobs (git based checkout, archiving all builds) seem to work just fine.

      But we have several jobs derived from the central git checkout job. And those have no source repository attached and builds are kept for 5 days and to a maximum of 10 builds.

      Changing the archival setting of these jobs does not seem to change anything. In fact the archival setting does not seem to take effect at all. Currently the jobs keep all the builds.

      Any suggestions on further steps I could take to identify the cause of the issue?

            Unassigned Unassigned
            gwrobel gwrobel
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: