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

notifyCommit holds changes for about an hour after Hudson restart

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • subversion-plugin
    • None

      We are currently on 1.383, but this issue has been around for the past 4 or 5 versions.

      We have a Subversion post-commit hook configured as per http://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin. Under normal operations this approach is rock solid. However, immediately after Hudson restarts SVN changes do not trigger builds.

      What appears to be happening is that Hudson receives the notifyCommit information correctly, but holds onto it for around an hour. For us the timing is very reproducible; all changes across different projects and svn branches seem to be held for right around an hour after restart. Once the hour is over, all of the related jobs appear in the queue and build as normal, and subsequent SVN updates trigger immediate builds.

      We've looked at logs but haven't seen anything indicating that the post-commit hook is being delayed. We've also tried debugging from the SVN side, re-running the post-commit hook and manually interacting with the notifyCommit URL, but Hudson seems to be returning successful status in all cases.

            Unassigned Unassigned
            tpesce Tim Pesce
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: