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

Changes doesn't trigger a build - "unknown revision"

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • multiple-scms-plugin
    • None
    • RHEL 6, Mercurial 1.4, Jenkins 1.452

      With two Mercurial repositories configured, even though the plug-in detects a changeset it still doesn't trigger a new build because it is referring to a (previous?) known revision.

      Here's the polling log from where it detects a change:

      Started on Feb 29, 2012 7:41:20 AM
      [public] $ /usr/bin/hg pull --rev default
      pulling from http://gbglcrd10/hg/jsf/
      searching for changes
      adding changesets
      adding manifests
      adding file changes
      added 1 changesets with 2 changes to 2 files
      (run 'hg update' to get a working copy)
      [public] $ /usr/bin/hg log --style /ssd/Jenkins/jobs/newjsf/workspace/tmp5480491059555742578style --branch default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
      abort: unknown revision '8ee1ae92f8aa040c970d64c992ece871b994dab9'!
      [private] $ /usr/bin/hg pull --rev default
      pulling from http://gbglcrd10/hg-jsf/licensing/
      no changes found
      [private] $ /usr/bin/hg log --style /ssd/Jenkins/jobs/newjsf/workspace/tmp4214498074041391865style --branch default --no-merges --prune 8ee1ae92f8aa040c970d64c992ece871b994dab9
      Done. Took 0.92 sec
      No changes

      Is this revision coming from the second configured repository? In any case, this always fails.

          [JENKINS-12927] Changes doesn't trigger a build - "unknown revision"

          The used unknown revision is remembered from the latest build, second configured repository:

          First repository (http://gbglcrd10/hg/jsf/): 93a43a50dcce0a74614454cb46de77b6645e5d8b
          Second repository (http://gbglcrd10/hg-jsf/licensing/): 8ee1ae92f8aa040c970d64c992ece871b994dab9

          It needs to remember revisions from both (all) configured repositories, not only the last.

          Marcus Eriksson added a comment - The used unknown revision is remembered from the latest build, second configured repository: First repository ( http://gbglcrd10/hg/jsf/): 93a43a50dcce0a74614454cb46de77b6645e5d8b Second repository ( http://gbglcrd10/hg-jsf/licensing/): 8ee1ae92f8aa040c970d64c992ece871b994dab9 It needs to remember revisions from both (all) configured repositories, not only the last.

          I'm having the same problem. It is quite a show stopper right now.

          Börje Granberg added a comment - I'm having the same problem. It is quite a show stopper right now.

          frew schmidt added a comment -

          I have the opposite problem with two git repos, that is, no changes and it still makes a build. I got around it by just not using the Multiple SCM plugin, setting up a single repo, and then using the shell to check out the other one and update it. Sucks though.

          frew schmidt added a comment - I have the opposite problem with two git repos, that is, no changes and it still makes a build. I got around it by just not using the Multiple SCM plugin, setting up a single repo, and then using the shell to check out the other one and update it. Sucks though.

          Lewis Pollard added a comment -

          Seems to get confused not just over revs but branches too - e.g. if I have repo A with branch 'dev' and repo B with branch 'staging' it tries to pull on repo B 'dev' branch. Shame that this appears not to be active any more as it would have been perfect.

          Lewis Pollard added a comment - Seems to get confused not just over revs but branches too - e.g. if I have repo A with branch 'dev' and repo B with branch 'staging' it tries to pull on repo B 'dev' branch. Shame that this appears not to be active any more as it would have been perfect.

          philippe_tseyen added a comment - - edited

          I think I'm hitting the same issue: I upgraded the mercurial plugin from 1.34 to 1.46.

          I had to downgrade to work around the issue. The weird part is that not all builds are failing: some tags are handled correctly.

          I'm on Jenkins LTS 1.509

          Started by user anonymous
          Building remotely on hlbsdev1 in workspace /opt/jenkins/workspace/aci-4.10-deploy
          [aci-4.10-deploy] $ hg showconfig paths.default
          [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint
          [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint
          abort: unknown revision 'r4.10.0_maint'!
          ERROR: Failed to update
          ERROR: Failed to update
          Retrying after 10 seconds
          [aci-4.10-deploy] $ hg showconfig paths.default
          [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint
          [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint
          abort: unknown revision 'r4.10.0_maint'!
          ERROR: Failed to update
          ERROR: Failed to update
          Retrying after 10 seconds
          [aci-4.10-deploy] $ hg showconfig paths.default
          [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint
          [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint
          abort: unknown revision 'r4.10.0_maint'!
          ERROR: Failed to update
          ERROR: Failed to update

          philippe_tseyen added a comment - - edited I think I'm hitting the same issue: I upgraded the mercurial plugin from 1.34 to 1.46. I had to downgrade to work around the issue. The weird part is that not all builds are failing: some tags are handled correctly. I'm on Jenkins LTS 1.509 Started by user anonymous Building remotely on hlbsdev1 in workspace /opt/jenkins/workspace/aci-4.10-deploy [aci-4.10-deploy] $ hg showconfig paths.default [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint abort: unknown revision 'r4.10.0_maint'! ERROR: Failed to update ERROR: Failed to update Retrying after 10 seconds [aci-4.10-deploy] $ hg showconfig paths.default [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint abort: unknown revision 'r4.10.0_maint'! ERROR: Failed to update ERROR: Failed to update Retrying after 10 seconds [aci-4.10-deploy] $ hg showconfig paths.default [aci-4.10-deploy] $ hg pull --rev r4.10.0_maint [aci-4.10-deploy] $ hg update --clean --rev r4.10.0_maint abort: unknown revision 'r4.10.0_maint'! ERROR: Failed to update ERROR: Failed to update

            kbell Kevin Bell
            marese Marcus Eriksson
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: