Marcus Eriksson created JENKINS-12927: -----------------------------------------
Summary: Changes doesn't trigger a build - "unknown revision" Key: JENKINS-12927 URL: https://issues.jenkins-ci.org/browse/JENKINS-12927 Project: Jenkins Issue Type: Bug Components: multiple-scms Affects Versions: current Environment: RHEL 6, Mercurial 1.4, Jenkins 1.452 Reporter: Marcus Eriksson Assignee: Kevin Bell 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira