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

List of changes for a build is empty even though mercurial plugin detects them!

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • mercurial-plugin
    • None

      Hi,

      I'm currently testing the cache feature of the mercurial plugin, although this is something that I have observed also without such cache enabled. We have a master (that does not performs builds), with several slave nodes which do the actual work of running our project's builds.

      The thing is that even though the mercurial plugin detects changes in the repository (as the mercurial polling log reports), the build that is triggered sometimes has an empty list of changes.

      And it looks like that it's not "sometimes" really, but with a given pattern I'm starting to see with my tests: when the mercurial plugin detects changes in the repository and triggers a build in a slave that already has a cloned local cache of the repository, then changes are successfully reported as part of the build information. Otherwise, when the build is triggered in a slave without an existing cache for the given repository, for example, that build has an empty list of changes.

      Considering that the mercurial plugin always seems to correctly detect that there are new changes that require a build, it's such a nuisance that we have empty changes lists for all those builds.

      Regards,
      David

          [JENKINS-11072] List of changes for a build is empty even though mercurial plugin detects them!

          Jesse Glick added a comment -

          Possible duplicate of JENKINS-10255.

          Jesse Glick added a comment - Possible duplicate of JENKINS-10255 .

          Yes, probably the fix for JENKINS-10255 would make the changes list to behave as expected in all situations.

          David Santiago Turiño added a comment - Yes, probably the fix for JENKINS-10255 would make the changes list to behave as expected in all situations.

          Yes, probably the fix for JENKINS-10255 would make the changes list to behave as expected in all situations.

          David Santiago Turiño added a comment - Yes, probably the fix for JENKINS-10255 would make the changes list to behave as expected in all situations.

          Generic Ratslaugh added a comment - - edited

          I'm clearly seeing this issue with Jenkins 1.549.
          I'm using multiple hg repositories. I trigger the build by polling for changes to any one of the repositories. This polling works fine and the changes are correctly reported by the Jenkins build instance dashboard and the changes do correctly appear in the workspace.
          However, the console log always reports "no changes found" and gives the revision information appropriate to the previous build. FWIW, if I subsequently manually trigger a build, then the manually triggered build reports the updated revision(s) (of course, as always, "no changes found").
          Update:
          Installed Jenkins 1.554.1 on RHEL 6.5 server. Still seeing this issue. Mercurial caching is not enabled on either machine.

          Generic Ratslaugh added a comment - - edited I'm clearly seeing this issue with Jenkins 1.549. I'm using multiple hg repositories. I trigger the build by polling for changes to any one of the repositories. This polling works fine and the changes are correctly reported by the Jenkins build instance dashboard and the changes do correctly appear in the workspace. However, the console log always reports "no changes found" and gives the revision information appropriate to the previous build. FWIW, if I subsequently manually trigger a build, then the manually triggered build reports the updated revision(s) (of course, as always, "no changes found"). Update: Installed Jenkins 1.554.1 on RHEL 6.5 server. Still seeing this issue. Mercurial caching is not enabled on either machine.

            kohsuke Kohsuke Kawaguchi
            nimeacuerdo David Santiago Turiño
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: