[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Nicolas De Loof commented on JENKINS-14201 Git submodules checked out in wrong place git plugin 1.3.0 uses JGit to fetch remote, can you please give it a try an report this issue still is relevant ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin commented on JENKINS-14201 Git submodules checked out in wrong place I have same issue after installing Analysis Collector Plugin and PMD Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin edited a comment on JENKINS-14201 Git submodules checked out in wrong place I have same issue after installing Analysis Collector Plugin and PMD Plugin Jenkins run git fetch for submodule with wrong working directory. Git plugin 1.1.9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Arkadiy Shapkin commented on JENKINS-14201 Git submodules checked out in wrong place Problem was solved after updating to latest Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU commented on JENKINS-14201 Git submodules checked out in wrong place I've met the same problem. And investigated, I've done creating a testcate to repeat the problem. see. https://github.com/comutt/git-plugin/commit/09d16e20592e206f2de64017bb2276124ba2d443 I'm new to Jenkins source code, so It'll take little time to fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU commented on JENKINS-14201 Git submodules checked out in wrong place To repeat the problem, try the following process: Init root repository Add submodule Under the added submodule, create the branch (In my case, create a branch from a tag, but this may not a cause of this problem) Create a project, with the root repository First build will succeed Second build (and builds after this) will corrupt the jenkins workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU commented on JENKINS-14201 Git submodules checked out in wrong place After some investigation, the initial clone causes the corrupt. On the initial cloning, hudson.plugins.git.GitSCM#fetchSubmodulesFrom is called. And then, hudson.plugins.git.IGitAPI#fetch (by subGit.fetch(submoduleRemoteRepository);) is called. After that, the result of tree command, which is for WORKSPACE/test0/.git, is: .git ├── FETCH_HEAD ├── HEAD ├── branches ├── config ├── description ├── hooks │ ├── applypatch-msg.sample │ ├── commit-msg.sample │ ├── post-update.sample │ ├── pre-applypatch.sample │ ├── pre-commit.sample │ ├── pre-rebase.sample │ ├── prepare-commit-msg.sample │ └── update.sample ├── index ├── info │ └── exclude ├── logs │ ├── HEAD │ └── refs │ ├── heads │ │ └── master │ └── remotes │ └── origin │ ├── b_tagOfModule1 │ └── master ├── objects │ ├── 27 │ │ └── 31d33c38b55dc717a0d644571eea30ec3a00e3 │ ├── 61 │ │ └── 064ef71976703c49eb13ece2030c89965b7145 │ ├── 66 │ │ └── 52ffc1ee608a2bf7be49b8ead0526182b1d52b │ ├── 82 │ │ └── 818b9b6f0420237a8c1a5e6e771e900b7a79d2 │ ├── 9d │ │ └── 7a672db165435d85eb807192b218cdcaed340f │ ├── a8 │ │ └── edc5644debf0e6600164c8fe13f83e785a9b1a │ ├── ca │ │ └── f1aee9a48387b6d9cbeab47958ed2def5a3bd1 │ ├── e6 │ │ ├── 46e34bbd8d13586015757ad5e227617c9513e8 │ │ └── 9de29bb2d1d6434b8b29ae775ad8c2e48c5391 │ ├── f8 │ │ └── 53768ca5aa9df82f889cda025f166bf59abdb4 │ ├── info │ └── pack ├── packed-refs └── refs ├── heads │ └── master ├── remotes │ └── origin │ ├── HEAD │ ├── b_tagOfModule1 │ └── master └── tags └── tagOfModule1 b_tagOfModule1 the above is may strange, because that is of submodule (module1) tag, not root's. A repository structure is created by the testcase I mentioned before: https://github.com/comutt/git-plugin/commit/09d16e20592e206f2de64017bb2276124ba2d443 And I apologize that I have no more time to investigate, and may not fix this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU commented on JENKINS-14201 Git submodules checked out in wrong place Also, If I'm wrong, I apologize for it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU
commented on JENKINS-14201
Git submodules checked out in wrong place
I'm sorry, that I'm wrong about the cause of this problem.
git fetch -f is executed when subtree merge done.
I investigate and compare the result with {clone, submodule init, submodule update} and git-plugin's {clone, fetch -f, ...}.
This is of course still problem, but my guess is entirely wrong, I'm sorry.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Seiji KOMATSU
edited a comment on JENKINS-14201
Git submodules checked out in wrong place
I'm sorry, that I'm wrong about the cause of this problem.
git fetch -f is executed when subtree merge done.
I investigated and compared the result with my {clone, submodule init, submodule update} and git-plugin's {clone, fetch -f, ...}.
This is of course still problem, but my guess is entirely wrong, I'm sorry.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Birkett edited a comment on JENKINS-14201 Git submodules checked out in wrong place Thanks for your comment Matt Willsher. How would one add a git checkout as a manual step? I can make Jenkins build my project if I wipe the workspace before each build and disable internal tagging. Appart from the unnecessary strain this puts on the git server, it breaks polling - the project get built after each poll, not just when changes are detected. This issue is still blocking me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Birkett commented on JENKINS-14201 Git submodules checked out in wrong place Thanks for your comment Matt Willsher. How would one add a git checkout as a manual step? I can make Jenkins build my project if I wipe the workspace before each build and disable internal tagging. Appart from the unnecessary strain this puts on the git server, it breaks polling - the project get built after each poll, not just when changes detected. This issue is still blocking me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Matt Willsher commented on JENKINS-14201 Git submodules checked out in wrong place I'm seeing the same issue, compounded by the fact that even clearing down the workspace doesn't resolve the problem. In the output below (censored for security/privacy reasons, intent is the same). origin/requirejs-2.0-upgrade is not part of REMOVEDPROJECT-pkg, but a branch in the submodule contained with in. This did work, but after changing the submodule locations and updating via git submodule sync each build gets the following error. Work around will be to add a git checkout as a manual step, so not entirely a blocker but a significant problem none the less. Jenkins ver. 1.473 Jenkins GIT plugin org.jenkinsci.plugins:git:1.1.21 annotation-indexer org.jvnet.hudson:annotation-indexer:1.2 Joda time joda-time:joda-time:1.5.1 JSchcom.jcraft:jsch:0.1.44-1 Bridge method injection com.infradna.tool:bridge-method-annotation:1.4 annotations JGit - Core org.eclipse.jgit:org.eclipse.jgit:0.12.1 Building remotely on RPM build slave 1 in workspace /home/jenkins/workspace/REMOVEDPROJECT-pkg Checkout:REMOVEDPROJECT-pkg / /home/jenkins/workspace/REMOVEDPROJECT-pkg - hudson.remoting.Channel@aef8664:RPM build slave 1 Using strategy: Default Last Built Revision: Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) Fetching changes from 1 remote Git repository Fetching upstream changes from git@gitlab.REMOVED:REMOVEDPROJECT-pkg.git Seen branch in repository origin/HEAD Seen branch in repository origin/master Commencing build of Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) Checking out Revision e0fb13e7b464d812a90d7d73b1df06cf09d27c56 (origin/requirejs-2.0-upgrade) FATAL: Could not checkout null with start point e0fb13e7b464d812a90d7d73b1df06cf09d27c56 hudson.plugins.git.GitException: Could not checkout null with start point e0fb13e7b464d812a90d7d73b1df06cf09d27c56 at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:931) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1285) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git checkout -f e0fb13e7b464d812a90d7d73b1df06cf09d27c56" returned status code 128: stdout: stderr: fatal: reference is not a tree: e0fb13e7b464d812a90d7d73b1df06cf09d27c56 at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:838) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:800) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:810) at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:918) ... 12 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Alex created JENKINS-14201 Git submodules checked out in wrong place Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 24/Jun/12 6:01 PM Description: The Phonelocator project, git://github.com/alexbirkett/phonelocator-android.git, has the following submodules: submodule HockeyKit path = HockeyKit url = ""> submodule cwac-locpoll path = cwac-locpoll url = ""> submodule ActionBarSherlock path = ActionBarSherlock url = ""> submodule android-controllers path = android-controllers url = ""> The first time Jenkins builds the project, everything appears to be checked out in the correct place. On subsequent builds, corruption occurs and files from one or more of the submodules appear in the root directory of the workspace. Environment: Jenkins ver. 1.447.2, Jenkins GIT plugin 1.1.19, Git version 1.7.9.5 Project: Jenkins Priority: Major Reporter: Alex Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Alex commented on JENKINS-14201 Git submodules checked out in wrong place This is the start of the console output for the first build: Started by user anonymous ln -s 2012-06-24_14-45-30 /var/lib/jenkins/jobs/jenkins-bug-test/builds/1 failed: -1 Checkout:workspace / /var/lib/jenkins/jobs/jenkins-bug-test/workspace - hudson.remoting.LocalChannel@1a88001 Using strategy: Default Cloning the remote Git repository Cloning repository origin Fetching upstream changes from git://github.com/alexbirkett/phonelocator-android.git Seen branch in repository origin/HEAD Seen branch in repository origin/master Commencing build of Revision fef2487972cdf21160ebd802c45669d244aba538 (origin/HEAD, origin/master) Checking out Revision fef2487972cdf21160ebd802c45669d244aba538 (origin/HEAD, origin/master) Trying to fetch ActionBarSherlock into /var/lib/jenkins/jobs/jenkins-bug-test/workspace/ActionBarSherlock Fetching upstream changes from git://github.com/alexbirkett/ActionBarSherlock.git Trying to fetch HockeyKit into /var/lib/jenkins/jobs/jenkins-bug-test/workspace/HockeyKit Fetching upstream changes from git://github.com/alexbirkett/HockeyKit.git Trying to fetch android-controllers into /var/lib/jenkins/jobs/jenkins-bug-test/workspace/android-controllers Fetching upstream changes from git://github.com/alexbirkett/android-controllers.git Trying to fetch cwac-locpoll into /var/lib/jenkins/jobs/jenkins-bug-test/workspace/cwac-locpoll Fetching upstream changes from git://github.com/alexbirkett/cwac-locpoll.git No change to record in branch origin/HEAD No change to record in branch origin/master build succeeds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Alex updated JENKINS-14201 Git submodules checked out in wrong place Change By: Alex Alex (24/Jun/12 6:05 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Alex commented on JENKINS-14201 Git submodules checked out in wrong place This is the entire console output for the second build: Started by user anonymous ln -s 2012-06-24_14-51-30 /var/lib/jenkins/jobs/jenkins-bug-test/builds/2 failed: -1 Checkout:workspace / /var/lib/jenkins/jobs/jenkins-bug-test/workspace - hudson.remoting.LocalChannel@1a88001 Using strategy: Default Last Built Revision: Revision fef2487972cdf21160ebd802c45669d244aba538 (origin/HEAD, origin/master) Fetching changes from 1 remote Git repository Fetching upstream changes from git://github.com/alexbirkett/phonelocator-android.git Seen branch in repository origin/HEAD Seen branch in repository origin/alex Seen branch in repository origin/android_controllers Seen branch in repository origin/android_controllers_support_library_version Seen branch in repository origin/dev Seen branch in repository origin/develop Seen branch in repository origin/gh-pages Seen branch in repository origin/jar Seen branch in repository origin/master Seen branch in repository origin/refactor_check_update_task Seen branch in repository origin/search-view Seen branch in repository origin/support_library Seen branch in repository origin/testing-buildhive Commencing build of Revision 49d1899e7bdfc77a6500524cc0dbb1b7146467e1 (origin/jar) Checking out Revision 49d1899e7bdfc77a6500524cc0dbb1b7146467e1 (origin/jar) No change to record in branch origin/jar FATAL: Unable to find build script at /var/lib/jenkins/jobs/jenkins-bug-test/workspace/phonelocator/build.xml Build step 'Invoke Ant' marked build as failure Archiving artifacts Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Alex updated JENKINS-14201 Git submodules checked out in wrong place Change By: Alex Alex (24/Jun/12 6:05 PM) Description: ThePhonelocatorproject,git://github.com/alexbirkett/phonelocator-android.git,hasthefollowingsubmodules:[submoduleHockeyKit] path=HockeyKit url=git://github.com/alexbirkett/HockeyKit.git[submodulecwac-locpoll] path=cwac-locpoll url=git://github.com/alexbirkett/cwac-locpoll.git[submoduleActionBarSherlock] path=ActionBarSherlock url=git://github.com/alexbirkett/ActionBarSherlock.git[submoduleandroid-controllers] path=android-controllers url=git://github.com/alexbirkett/android-controllers.gitThefirsttimeJenkinsbuildstheproject,everythingappearstobecheckedoutinthecorrectplace.Onsubsequentbuilds,corruptionoccursandfilesfromoneormoreofthesubmodulesappearintherootdirectoryoftheworkspace. Seecommentsforconsoleoutput This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14201) Git submodules checked out in wrong place
Alex Birkett commented on JENKINS-14201 Git submodules checked out in wrong place I have a zip of the workspace after the first and second builds. They're too big to upload but let me know if there are useful and I can get them to you some other way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
