• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: All

      It appears with the recent fixes to the subversion features that its broken
      something todo with triggering builds.

      What it appears to be doing is detecting that the repository revision # has
      changed and starts a build. When that build finishes however, hudson doesn't
      update the revision #. As a result, in the next poll of the SCM hudson builds
      again. For whatever reason, on the second attempt, hudsons revision number is
      correctly updated.

      The result is duplicate builds for every SCM checkin using Subversion

          [JENKINS-692] Job Builds from subversion are building twice

          gommo created issue -

          Any chance you can post the relevant portions of the console log and SVN polling
          log?

          Kohsuke Kawaguchi added a comment - Any chance you can post the relevant portions of the console log and SVN polling log?
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

              • Issue 688 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 688 has been marked as a duplicate of this issue. ***
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-688 [ JENKINS-688 ]

          Improved the polling output message to indicate what is the current revision
          that Hudson thinks, and what is the new revision it got from the remote
          repository. This change will be in 1.125.

          Adding stanoislav to the CC list as he reported issue #688.

          Kohsuke Kawaguchi added a comment - Improved the polling output message to indicate what is the current revision that Hudson thinks, and what is the new revision it got from the remote repository. This change will be in 1.125. Adding stanoislav to the CC list as he reported issue #688.

          gommo added a comment -

          Just some added info.

          First build
          started
          Updating http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk
          At revision 12700
          no change for http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk
          since the previous build
          [trunk] $ cmd.exe /C D:\BuildServer\ant\apache-ant-1.7.0\bin\ant.bat
          devAutoBuild -DANT_OPTS=-Xmx512m -buildfile util/build.xml && exit %%ERRORLEVEL%%
          Buildfile: util\build.xml

          The second build

          started
          Updating http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk
          U .classpath
          D lib/testng-5.4-jdk14.jar
          lib
          A lib-tests
          AU lib-tests/testng-5.5-jdk14.jar
          AU lib-tests/clover.jar
          A lib-tests/clover.license
          AU lib-tests/cenquatasks.jar
          U util/dev.config.properties-template
          U util/build.xml
          util
          U
          At revision 12701
          [trunk] $ cmd.exe /C D:\BuildServer\ant\apache-ant-1.7.0\bin\ant.bat
          devAutoBuild -DANT_OPTS=-Xmx512m -buildfile util/build.xml && exit %%ERRORLEVEL%%
          Buildfile: util\build.xml

          The 1st build looks like it should never have occured because it was a change on
          another branch.

          gommo added a comment - Just some added info. First build started Updating http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk At revision 12700 no change for http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk since the previous build [trunk] $ cmd.exe /C D:\BuildServer\ant\apache-ant-1.7.0\bin\ant.bat devAutoBuild -DANT_OPTS=-Xmx512m -buildfile util/build.xml && exit %%ERRORLEVEL%% Buildfile: util\build.xml The second build started Updating http://10.20.1.21/svn/repos/minesuite/minesuite4/minesuite/trunk U .classpath D lib/testng-5.4-jdk14.jar lib A lib-tests AU lib-tests/testng-5.5-jdk14.jar AU lib-tests/clover.jar A lib-tests/clover.license AU lib-tests/cenquatasks.jar U util/dev.config.properties-template U util/build.xml util U At revision 12701 [trunk] $ cmd.exe /C D:\BuildServer\ant\apache-ant-1.7.0\bin\ant.bat devAutoBuild -DANT_OPTS=-Xmx512m -buildfile util/build.xml && exit %%ERRORLEVEL%% Buildfile: util\build.xml The 1st build looks like it should never have occured because it was a change on another branch.

          I tested this with my subversion repository but it appears to be working
          correctly. Does anyone still experience the issue?

          If so, please check the polling logs and paste them here. Whenever it detects
          changes, it will report details that help the trouble-shooting.

          Also, please check http://server/hudson/log, which indicates what builds are
          triggered by SCM polling and when. (1.128 contains log message improvements in
          this field.)

          Changing the priority as it seems to work in some environments, at least.

          Kohsuke Kawaguchi added a comment - I tested this with my subversion repository but it appears to be working correctly. Does anyone still experience the issue? If so, please check the polling logs and paste them here. Whenever it detects changes, it will report details that help the trouble-shooting. Also, please check http://server/hudson/log , which indicates what builds are triggered by SCM polling and when. (1.128 contains log message improvements in this field.) Changing the priority as it seems to work in some environments, at least.

          tblack added a comment -

          We experience this issue intermittently, it seems, with v1.149. I will try to
          capture the logs the next time I see it happen.

          tblack added a comment - We experience this issue intermittently, it seems, with v1.149. I will try to capture the logs the next time I see it happen.

          rodym added a comment -

          We experienced this in version 1.242 using CVS instead of subversion. We'll try
          to scan the logs.

          rodym added a comment - We experienced this in version 1.242 using CVS instead of subversion. We'll try to scan the logs.

            Unassigned Unassigned
            gommo gommo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: