• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Jenkins server running on Windows XP with slaves on XP, 7, and RHEL 5.

      For the third time this week, when I arrived at work today Jenkins had lost all of our build history. (This also happened one other time a couple weeks ago right after I upgraded to 1.558). There are no builds saved on disk on the master machine, and every job shows no builds. When they get launched, they start from the proper number (#700 in one case) - but all existing history is gone.

      The logs are confusing. I have two logs from January, and the rest of the logs are filled with the following-

      May 14, 2014 2:29:37 AM jenkins.model.lazy.AbstractLazyLoadRunMap search
      WARNING: JENKINS-15652 Assertion error #1: failing to load C:\Jenkins\workspace\builds\REUSE_Unit_Tests\CONFIG=ut_intPPCSim, TEST=Aes_UT, label=LOCAL
      #350 EXACT: lo=1,hi=0,size=1,size2=1
      May 14, 2014 2:29:37 AM jenkins.model.lazy.AbstractLazyLoadRunMap search
      WARNING: JENKINS-15652 Assertion error #1: failing to load C:\Jenkins\workspace\builds\REUSE_Unit_Tests\CONFIG=ut_intPPCSim, TEST=Aes_UT, label=LOCAL
      #351 DESC: lo=1,hi=0,size=1,size2=1

      Those two warnings are just repeated over and over for each job- filling 8 log files in the space of a couple minutes. I have no other clues to go off of, but I need to figure out what is going on here.

          [JENKINS-23067] Jenkins losing build history

          Daniel Beck added a comment -

          These are matrix (multi-config) projects, right? Do you have other project types as well? Are they affected? What's the version of the Matrix Project plugin you have installed? If possible, please update the plugin.

          Daniel Beck added a comment - These are matrix (multi-config) projects, right? Do you have other project types as well? Are they affected? What's the version of the Matrix Project plugin you have installed? If possible, please update the plugin.

          Paul Becotte added a comment -

          Yes, I have other project types that were affected. It was not 100% universal- some of the other jobs kept one or two builds in history (out of many), but the matrix jobs and the jobs related to them (upstream) lost everything.

          I went ahead and upgraded to the new version of Jenkins and the matrix plugin. The history was completely gone again this morning with 1.563 Jenkins and 1.2 Matrix plugin.

          I realized that my builds and workspace directory for the masters config.xml were set to non-standard locations. I changed them to match my other Jenkins server and am hoping that this may clear up the issue.

          Paul Becotte added a comment - Yes, I have other project types that were affected. It was not 100% universal- some of the other jobs kept one or two builds in history (out of many), but the matrix jobs and the jobs related to them (upstream) lost everything. I went ahead and upgraded to the new version of Jenkins and the matrix plugin. The history was completely gone again this morning with 1.563 Jenkins and 1.2 Matrix plugin. I realized that my builds and workspace directory for the masters config.xml were set to non-standard locations. I changed them to match my other Jenkins server and am hoping that this may clear up the issue.

          Daniel Beck added a comment -

          There've been issues with these options in the past (e.g. build dir not renamed when project is renamed).

          Daniel Beck added a comment - There've been issues with these options in the past (e.g. build dir not renamed when project is renamed).

          Paul Becotte added a comment -

          Since I changed the storage location back to the standard location, this has not happened again. I believe you could tentatively close this for now, and I will come back if the problem does happen again.

          Paul Becotte added a comment - Since I changed the storage location back to the standard location, this has not happened again. I believe you could tentatively close this for now, and I will come back if the problem does happen again.

          Paul Becotte added a comment -

          Changed storage location of the "builds" directory to the default. Have not seen the issue since.

          Paul Becotte added a comment - Changed storage location of the "builds" directory to the default. Have not seen the issue since.

          Daniel Beck added a comment -

          Do you still know the values you entered for workspace + builds dir in the global Jenkins config? I'm currently working on improving their input validation, it's far too easy to enter really wrong values (JENKINS-14583).

          Daniel Beck added a comment - Do you still know the values you entered for workspace + builds dir in the global Jenkins config? I'm currently working on improving their input validation, it's far too easy to enter really wrong values ( JENKINS-14583 ).

            Unassigned Unassigned
            pbecotte Paul Becotte
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: