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

SCM check via subversion continues triggering new builds - even with no changes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Debian 8.3.0 on AMD 64Bit Intel DN2800MT2 hardware, headless server, dedicated to Jenkins. SVN hosted on different dedicated hardware. No virtualization.

      Running latest version of Jenkins (1.652) and SVN Plugin (2.5.7).
      I configured five Matrix projects with dimension OS = linux windows and BIT = 32 64

      I noticed that my machine got building 24/7 not able to clear the stack once I updated to the latest versions indicated in Jenkins configuration. All worked fine and well in the previous version.
      I checked the reason and figured out that Jenkins checked the SCM using SVN Plugin once per hour (as I configured), but claimed an SVN change each time (in the log) triggering the build. However, the revision number stayed the same!

      here is what the config tells me about the trigger (locales in german, you get the idea from the english part I am sure):
      Started on 12.03.2016 09:29:00
      Arbeitsbereich enthält https://<my_svn_server_domain>.org:443/repos/<myProjectName>/trunk nicht. Neuer Build erforderlich.
      Done. Took 0,17 Sekunden
      Changes found
      It checks the svn and complains it would not be in the working directory. Well, in the beginning, I had it removed before building the project to guarantee a clean environment each time. I also had a post-build step included to shred the directory as I was not keen on keeping my sourcecode on the harddrive. Well, I removed both, so there is nothing removed in the beginning and the post-build step is deleted completely.
      Jenkins continued to build in a loop.

      I then got on the console, stopped jenkins and cleared the directory of the Job - just keeping the bare config xml file. Starting from scratch, I hoped I could remove the ongoing builds. Nope, it continued.
      I then saw the pinned flag in the plugins and removed it, using a rather old version of the plugin - labeled 1.5.4. Jenkins continues to build in a loop.

      Dear community, I really like Jenkins and am happy of how it keeps running. Any ideas on how I can stop this issue still using the 'check SCM + svn plugin'? It is the best thing for us to have it checked once per hour. My small dev-group is not keen on using svn-hooks or such things as a workaround, yet lazy to push the button manually.

            Unassigned Unassigned
            jacknob Lars Engelhard
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: