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

Build history is inconsistent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      The build history for a project sometimes reports duplicate entries for a build
      and/or gets the build number incorrect. The contents of the Build History panel
      toggles between two sets of data:

      Build History
      Failed #109 Feb 10, 2008 8:03:32 PM
      Failed #109 Feb 10, 2008 8:03:32 PM
      Success #108 Feb 12, 2008 3:35:59 AM
      Failed #107 Feb 11, 2008 4:04:19 AM
      Failed #106 Feb 10, 2008 8:03:31 PM
      Success #105 Feb 10, 2008 3:34:11 AM

      And then the output toggles to this upon refresh:

      Build History
      Failed #109 Feb 10, 2008 8:03:32 PM
      Success #108 Feb 12, 2008 3:35:59 AM
      Failed #107 Feb 11, 2008 4:04:19 AM
      Failed #106 Feb 10, 2008 8:03:31 PM
      Success #105 Feb 10, 2008 3:34:11 AM

      The next refresh returns the contents back to the first set of data.

      This is from v1.176. I checked the changelog and did not see any fixes
      pertaining to this issue.

      Relevant info:
      a. The project in question is dependent on another project (and in turn has a
      project that is dependent on it). I don't know if that has anything to do with
      the error or not.
      b. The system is configured for only one build executor
      c. The project is configured to poll subversion with the following pattern: 0
      */4 * * *
      d. The nextBuildNumber for the project is set to 109
      e. The builds directory contains (among others) the following subdirs
      2008-02-12_03-35-59
      2008-02-11_04-04-19
      2008-02-10_20-03-31
      2008-02-10_20-03-32
      2008-02-10_03-34-11
      f. The log contents of the 2008-02-10_20-03-31 build look good.
      g. The log contents of the 2008-02-10_20-03-32 build indicates a failure:
      started
      Updating http:<removed by jb>
      ERROR: Failed to update <removed by jb>
      org.tmatesoft.svn.core.SVNException: svn: Working copy '<removed by jb>' locked;
      try performing 'cleanup'
      at
      org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:49)
      at
      org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.lock(SVNAdminArea14.java:1370)
      at
      org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:348)
      at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:261)
      at
      org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:153)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:145)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:384)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:356)
      at hudson.FilePath.act(FilePath.java:291)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:353)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:299)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:558)
      at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:223)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:189)
      at hudson.model.Run.run(Run.java:656)
      at hudson.model.Build.run(Build.java:102)
      at hudson.model.ResourceController.execute(ResourceController.java:70)
      at hudson.model.Executor.run(Executor.java:65)
      finished: FAILURE

      I'll be happy to provide any other information you need.

      jb

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

              Created:
              Updated:
              Resolved: