-
Bug
-
Resolution: Duplicate
-
Major
-
None
The git plug-in provides an option to specify multiple repositories, however the files are not checked out into different folders. Even if I specify the name for the repository this name seems not to be used. It seems some kind of random which repository wins during the checkout.
Expected behavior: If I specify the two repositories
- git://github.com/jenkinsci/analysis-pom-plugin.git (Name: analysis-pom)
- git://github.com/jenkinsci/analysis-suite-plugin.git (Name analysis-suite)
then the file system structure should be the same as with the subversion plugin:
- workspace/analysis-pom
- workspace/analysis-suite
Actual file system structure:
workspace/src (where src is from the checkstyle plug-in)
Here the log of my build:
Started by user anonymous Checkout:workspace / /home/hudson/Hudson/jobs/Suite (Compile)/workspace - hudson.remoting.LocalChannel@67a309 Using strategy: Default Last Built Revision: Revision 06abd1ccb6bd29307156079a132fd0d5497348a6 (origin5/master) Checkout:workspace / /home/hudson/Hudson/jobs/Suite (Compile)/workspace - hudson.remoting.LocalChannel@67a309 Fetching changes from the remote Git repository Fetching upstream changes from git://github.com/jenkinsci/analysis-pom-plugin.git Fetching upstream changes from git://github.com/jenkinsci/analysis-suite-plugin.git Fetching upstream changes from git://github.com/jenkinsci/analysis-core-plugin.git Fetching upstream changes from git://github.com/jenkinsci/checkstyle-plugin.git Fetching upstream changes from git://github.com/jenkinsci/dry-plugin.git Fetching upstream changes from git://github.com/jenkinsci/pmd-plugin.git Fetching upstream changes from git://github.com/jenkinsci/tasks-plugin.git Fetching upstream changes from git://github.com/jenkinsci/warnings-plugin.git Seen branch in repository origin4/master Seen branch in repository origin2/svn Seen branch in repository origin/svn Seen branch in repository origin5/master Seen branch in repository origin5/svn Seen branch in repository origin6/master Seen branch in repository origin1/svn Seen branch in repository origin2/master Seen branch in repository origin7/svn Seen branch in repository origin4/svn Seen branch in repository origin3/master Seen branch in repository origin7/master Seen branch in repository origin3/svn Seen branch in repository origin/master Seen branch in repository origin6/svn Seen branch in repository origin1/master Commencing build of Revision 7d9bb8e92b2d4042d6b3c0ced541727d7434a8bb (origin3/master) Checking out Revision 7d9bb8e92b2d4042d6b3c0ced541727d7434a8bb (origin3/master) No change to record in branch origin3/master [workspace] $ /home/hudson/Hudson/tools/2.2.1/bin/mvn -f analysis-suite/pom.xml clean install -Dmaven.test.failure.ignore=true [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Default Project [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 second [INFO] Finished at: Thu Mar 03 09:13:08 CET 2011 [INFO] Final Memory: 2M/70M [INFO] ------------------------------------------------------------------------ Recording test results
- duplicates
-
-
- Closed
-