• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • mercurial-plugin
    • None
    • HG 2.0.1 / Jenkins 1.456 / Plugin 1.3.8

      I hate to bring such conflicting information into a bug report but I'm at a loss on this!

      This only happens for this one repo - I've deleted and re-created it, and setup from scratch with no joy.

      HG SCM Poll log insists it's finding changes and is firing a build off of 'Dependent changes detected'.

      Started on Mar 19, 2012 11:00:24 PM
      [src] $ hg pull --rev default
      pulling from /var/hg/repos/mpl
      no changes found
      [src] $ hg log --style /var/lib/jenkins/jobs/mpl/workspace/tmp2857899180971434423style --branch default --no-merges --prune 9c80c470fa3ef8d89c2352c08babb3f466b9aa24
      id:5b02d29a94c43648da2eb0a16f12c2e42eb46c87
      files:build.xml:
      Dependent changes detected
      Done. Took 0.21 sec
      Changes found

      There's no open/un-merged heads in the repo either:
      default 141:9c80c470fa3e

      If I downgrade to 1.3.7, it works fine (seems to run a different technique)

      HG SCM Poll log from 1.3.7:

      Started on Mar 19, 2012 11:11:14 PM
      [src] $ hg incoming --style /var/lib/jenkins/jobs/mpl/workspace/tmp1826463261407545325style --no-merges --rev default --newest-first
      comparing with /var/hg/repos/mpl
      no changes found
      Done. Took 53 ms
      No changes

          [JENKINS-13149] SCM Poll causing non-stop builds

          Same thing on my side.

          Maybe this info can help:
          The polled repo contains a sub-repo in which there are large files (files tagged with --large mercurial extension)

          Olivier Trempe added a comment - Same thing on my side. Maybe this info can help: The polled repo contains a sub-repo in which there are large files (files tagged with --large mercurial extension)

          Kayla Nimis added a comment -

          I'm having the same issue, the files that it says have changed were removed from the repo some time ago.

          Kayla Nimis added a comment - I'm having the same issue, the files that it says have changed were removed from the repo some time ago.

          Jesse Glick added a comment -

          Subrepos are not yet supported (JENKINS-4838). No idea how the plugin behaves with the largefiles extension, but probably there are bugs; certainly interaction with this plugin is not tested.

          Jesse Glick added a comment - Subrepos are not yet supported ( JENKINS-4838 ). No idea how the plugin behaves with the largefiles extension, but probably there are bugs; certainly interaction with this plugin is not tested.

          Mirela B added a comment -

          I have the same issue with the latest version of jenkins(1.462) and perforce plugin(1.3.1)
          pooling log:
          No changes found.
          Done. Took 5 min 42 sec
          Changes found

          Mirela B added a comment - I have the same issue with the latest version of jenkins(1.462) and perforce plugin(1.3.1) pooling log: No changes found. Done. Took 5 min 42 sec Changes found

          Ronen Peleg added a comment - - edited

          I have similar issue with continuous build (Jenkins 1.472).

          scm-polling log:
          Workspace doesn't contain http://svn-server.xyz.net/svn/MyProduct. Need a new build.
          Done. Took 0.28 sec
          Changes found

          Update: Solved!

          Ronen Peleg added a comment - - edited I have similar issue with continuous build (Jenkins 1.472). scm-polling log: Workspace doesn't contain http://svn-server.xyz.net/svn/MyProduct . Need a new build. Done. Took 0.28 sec Changes found Update: Solved!

          Rory Kingan added a comment - - edited

          I also experienced this problem but resolved it by getting rid of closed heads in my branch, as described below.

          I have two jobs polling the same repository, one looks at the default branch (and experiences this problem) and the other looks at a different branch and doesn't have this problem.

          The Mercurial Polling Log looks like this for the job that fails.

          Started on 29-Aug-2012 13:15:34
          [sources] $ hg pull --rev default
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          pulling from https://build_username@bitbucket.org/rory_kingan/rm_dev
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          no changes found
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting)
          [sources] $ hg log --style "C:\Program Files (x86)\Jenkins\jobs\rm_dev\workspace\tmp5625191036952426754style" --branch default --no-merges --prune cd316d1d748736c5d36d113dda1a87af275c5226
          id:00c102bbf7d0b012550c26cbca9a48c3c48eff2b
          files:Code/Sundi... LIST OF FILES HERE...:
          id:c1109d0cd1b75c26899856decd0717d37e37e4f2
          files:Code/Sundi... LIST OF FILES HERE...:
          id:4e6f64bfa355542e857cb315f15fba537885dd63
          files:Code/Sundi... LIST OF FILES HERE...:
          id:77902d778f52875b624fc18b9760ad295093239f
          files:Code/Sundi... LIST OF FILES HERE...:
          id:e7b1f9d32e46b99a11443d13c9dc2973dce9527d
          files:Code/Sundi... LIST OF FILES HERE...:
          id:85a021f78f2c2f1908403bab2a64e0db95fb8e4e
          files:.hgtags:
          id:6eefa3cdb0843fda9c59d56d430e0a77f4ebabe2
          files:Code/Sundi... LIST OF FILES HERE...:
          id:379762d7b1d909b99cb1cb0905918a13e463e8a0
          files:Code/Sundi... LIST OF FILES HERE...:
          id:c181dbccbf8495bec5f4699d4b1489d7f8e50a76
          files:Code/Sundi... LIST OF FILES HERE...:
          Dependent changes detected
          Done. Took 7.3 sec
          Changes found

          Based on the files that were listed in those supposed changes it looks like they're from closed heads.

          If I go to my repository folder locally, which is up to date on default branch and do
          > hg summary
          then it tells me the parent revision, in my case cd316d1d7487.
          If I then see what that hg log command will output
          > hg log --branch default --no-merges --prune cd316d1d7487
          I find it lists a bunch of old changesets on Closed heads on the default branch. We had these from some dodgy merging someone did ages back. We closed the head but clearly hg still sees it when performing an 'hg log', hence Jenkins thinks it's something new and that it needs to do a build.

          I resolved this problem for our repository by finding those changesets and merging them in to my default branch, using the option to discard all changes (I used TortoiseHg so not sure what the command-line option was). Then when I did the 'hg log ... --prune...' command there were no changesets listsed, and bingo, problem fixed on Jenkins too.

          Possibly Jenkins could avoid this issue by using a different hg command that ignores closed heads. Or possibly the best solution is just to not have other heads in your branch.

          Rory Kingan added a comment - - edited I also experienced this problem but resolved it by getting rid of closed heads in my branch, as described below. I have two jobs polling the same repository, one looks at the default branch (and experiences this problem) and the other looks at a different branch and doesn't have this problem. The Mercurial Polling Log looks like this for the job that fails. Started on 29-Aug-2012 13:15:34 [sources] $ hg pull --rev default warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) pulling from https://build_username@bitbucket.org/rory_kingan/rm_dev warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) no changes found warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) warning: bitbucket.org certificate with fingerprint 24:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified (check hostfingerprints or web.cacerts config setting) [sources] $ hg log --style "C:\Program Files (x86)\Jenkins\jobs\rm_dev\workspace\tmp5625191036952426754style" --branch default --no-merges --prune cd316d1d748736c5d36d113dda1a87af275c5226 id:00c102bbf7d0b012550c26cbca9a48c3c48eff2b files:Code/Sundi... LIST OF FILES HERE...: id:c1109d0cd1b75c26899856decd0717d37e37e4f2 files:Code/Sundi... LIST OF FILES HERE...: id:4e6f64bfa355542e857cb315f15fba537885dd63 files:Code/Sundi... LIST OF FILES HERE...: id:77902d778f52875b624fc18b9760ad295093239f files:Code/Sundi... LIST OF FILES HERE...: id:e7b1f9d32e46b99a11443d13c9dc2973dce9527d files:Code/Sundi... LIST OF FILES HERE...: id:85a021f78f2c2f1908403bab2a64e0db95fb8e4e files:.hgtags: id:6eefa3cdb0843fda9c59d56d430e0a77f4ebabe2 files:Code/Sundi... LIST OF FILES HERE...: id:379762d7b1d909b99cb1cb0905918a13e463e8a0 files:Code/Sundi... LIST OF FILES HERE...: id:c181dbccbf8495bec5f4699d4b1489d7f8e50a76 files:Code/Sundi... LIST OF FILES HERE...: Dependent changes detected Done. Took 7.3 sec Changes found Based on the files that were listed in those supposed changes it looks like they're from closed heads. If I go to my repository folder locally, which is up to date on default branch and do > hg summary then it tells me the parent revision, in my case cd316d1d7487. If I then see what that hg log command will output > hg log --branch default --no-merges --prune cd316d1d7487 I find it lists a bunch of old changesets on Closed heads on the default branch. We had these from some dodgy merging someone did ages back. We closed the head but clearly hg still sees it when performing an 'hg log', hence Jenkins thinks it's something new and that it needs to do a build. I resolved this problem for our repository by finding those changesets and merging them in to my default branch, using the option to discard all changes (I used TortoiseHg so not sure what the command-line option was). Then when I did the 'hg log ... --prune...' command there were no changesets listsed, and bingo, problem fixed on Jenkins too. Possibly Jenkins could avoid this issue by using a different hg command that ignores closed heads. Or possibly the best solution is just to not have other heads in your branch.

          Kieran Webber added a comment -

          This is still an issue for me for my current mercurial setup. Triggers a lot of unrequired builds

          Kieran Webber added a comment - This is still an issue for me for my current mercurial setup. Triggers a lot of unrequired builds

            jglick Jesse Glick
            rovangju Justin Rovang
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: