Community
Participate
Working Groups
Created attachment 240213 [details] Build Log using Multiple SCM to pull a few mercurial repositories While configuring a build job which pulled multiple mercurial repositories to build (with Multiple SCM installed), the build failed and the log showed that the following pulling is overwriting the previous one and thus the build area could not have the complete source from all repositories (detailed log is in attachment). The version of Multiple SCM plug-in is 0.2-h1. The plug-in works with Jenkins with same setting and build succeeded. $ hg clone --rev default --noupdate http://hg.openjdk.java.net/jdk9/dev /var/lib/hudson/jobs/jdk9-dev-build/workspace requesting all changes adding changesets adding manifests adding file changes added 968 changesets with 1410 changes to 137 files [workspace] $ hg update --rev default 81 files updated, 0 files merged, 0 files removed, 0 files unresolved [workspace] $ hg log --rev . --template {node} [workspace] $ hg log --rev . --template {rev} WARN: Revision data for previous build unavailable; unable to determine change log [workspace] $ hg showconfig paths.default ERROR: Workspace reports paths.default as http://hg.openjdk.java.net/jdk9/dev which looks different than http://hg.openjdk.java.net/jdk9/dev/jdk so falling back to fresh clone rather than incremental update $ hg clone --rev default --noupdate http://hg.openjdk.java.net/jdk9/dev/jdk /var/lib/hudson/jobs/jdk9-dev-build/workspace requesting all changes adding changesets adding manifests adding file changes added 9291 changesets with 86869 changes to 26485 files [workspace] $ hg update --rev default 22162 files updated, 0 files merged, 0 files removed, 0 files unresolved [workspace] $ hg log --rev . --template {node} [workspace] $ hg log --rev . --template {rev} WARN: Revision data for previous build unavailable; unable to determine change log
Can you please attach you job config XML. Thanks.
Created attachment 242109 [details] Job config file using Multiple SCM plugin Job config file using Multiple SCM attached.