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

Builds disappear from the history of slave builds (both from the HDD and GUI)

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hello,

      I'm using Jenkins v 1.517 and I'm experiencing a problem with disappearing history of slave builds. All builds are available in jobname\builds\ folder, however, the history of slave builds in jobname\configurations\axis-name\workspacename\builds\ is "periodically" purged. Some older jobs simply disappears from the list of builds (physically disappears from the HDD and GUI).

      Please see the attached screenshots (disappeared history of builds on slave machine) from last week and from today. I checked the history yesterday and there were all builds from 8.6. to 12.6. Today, there are only builds from 11.6. to 13.6.

      I can't find anything wrong in the build logs pointing to the history purge. Any idea what could be a cause of the history deletion? Is there a setting in Jenkins that could cause the purge of build history?

      Here is the list of installed plugins and their versions...
      ant 1.2
      backup 1.6.1
      chucknorris 0.5
      conditional-buildstep 1.2.2
      credentials 1.4
      cvs 2.9
      email-ext 2.30.2
      external-monitor-job 1.1
      git 1.4.0
      git-client 1.0.6
      javadoc 1.1
      jira 1.35
      ldap 1.4
      mailer 1.5
      maven-plugin 1.517
      msbuild 1.17
      multiple-scms 0.2
      pam-auth 1.1
      run-condition 0.10
      ssh-credentials 0.3
      ssh-slaves 0.25
      subversion 1.50
      token-macro 1.7
      translation 1.10
      vmware 0.8
      vsphere-cloud 0.10

      Thank you in advance!
      Pavel Kudrys

        Attachments

          Activity

          Hide
          jkregeramplify Julia Kreger added a comment -

          I'm seeing something very similar on 1.517 where all of the history and status for some, but not all jobs will just disappear. I have an identical server that has no build slaves where this issue has not been reported, however on a server that has multiple build slaves, and this is being encountered at least once a week, possibly twice a week much to my developer's frustrations.

          All slaves are JNLP launched. All hosts are Linux. OpenJDK 1.6. Build history files can be found on disk on the master, but are not listed in the gui. Jobs are configured to retain artifacts for 5 builds, and history for 20 builds. Matrix permissions are in use.

          ant
          credentials 1.4
          cvs 2.8
          email-ext 2.28
          external monitor job 1.1
          git 1.3.0
          git-client 1.0.5
          javadoc 1.1
          jira 1.35
          mailer 1.4
          maven-plugin 1.512
          pam-auth 1.0
          ssh-credentials 0.3
          ssh-slaves 0.25
          jenkins translation 1.10
          token-macro 1.6

          Show
          jkregeramplify Julia Kreger added a comment - I'm seeing something very similar on 1.517 where all of the history and status for some, but not all jobs will just disappear. I have an identical server that has no build slaves where this issue has not been reported, however on a server that has multiple build slaves, and this is being encountered at least once a week, possibly twice a week much to my developer's frustrations. All slaves are JNLP launched. All hosts are Linux. OpenJDK 1.6. Build history files can be found on disk on the master, but are not listed in the gui. Jobs are configured to retain artifacts for 5 builds, and history for 20 builds. Matrix permissions are in use. ant credentials 1.4 cvs 2.8 email-ext 2.28 external monitor job 1.1 git 1.3.0 git-client 1.0.5 javadoc 1.1 jira 1.35 mailer 1.4 maven-plugin 1.512 pam-auth 1.0 ssh-credentials 0.3 ssh-slaves 0.25 jenkins translation 1.10 token-macro 1.6
          Hide
          ntshako Hannes Kogler added a comment -

          same problem here.

          We are using 1.518

          Show
          ntshako Hannes Kogler added a comment - same problem here. We are using 1.518
          Hide
          danielbeck Daniel Beck added a comment -

          Can this be reproduced in recent versions of Jenkins? Does this only affect Matrix projects? Did you change the builds directory in the global Jenkins configuration? Did you configure to delete old builds in the job configuration? If so, what are the build deletion rules?

          Show
          danielbeck Daniel Beck added a comment - Can this be reproduced in recent versions of Jenkins? Does this only affect Matrix projects? Did you change the builds directory in the global Jenkins configuration? Did you configure to delete old builds in the job configuration? If so, what are the build deletion rules?
          Hide
          danielbeck Daniel Beck added a comment -

          No response to comment asking for additional information in months, so resolving as Incomplete.

          Show
          danielbeck Daniel Beck added a comment - No response to comment asking for additional information in months, so resolving as Incomplete.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            odklizec Pavel Kudrys
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: