hudson.plugins.git.GitException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • GitHub comment 157#156978211
    via GitHub by joshuajorel
    ,
  • I wanted to use the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ). I configured my job a described with the integration branch (Branch to merge to) configured to "developAutoMerge" and leaved the 'branch' field in the Git SCM blank. When I "Build now" I get following exception: Fetching changes from the remote Git repository Fetching upstream changes from git@REPOSITORY.git Seen branch in repository origin/develop Seen branch in repository origin/developAutoMerge Seen branch in repository origin/feature/blabla [...] Seen branch in repository origin/master Seen branch in repository origin/release/2.6.1 Seen branch in repository origin/release/2.6.2 Seen 13 remote branches Multiple candidate revisions Scheduling another build to catch up with blaServerBuild_developAutoMerge Merging Revision 6474f8ef91822e58edc55aad707d2725ff5a8431 (origin/feature/blabla) onto /developAutoMerge using resolve strategy FATAL: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128: stdout: /developAutoMerge^{commit} stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions hudson.plugins.git.GitException: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128: stdout: /developAutoMerge^{commit} stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:947) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:401) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:62) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:795) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:862) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) I found a similar problem by googling: https://groups.google.com/forum/#!topic/jenkinsci-dev/ek4hYR-z08k The proposed solution there was downgrading the Jenkins Git plugin from 2.0 to 1.4.0.
    via by m r,
  • I wanted to use the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ). I configured my job a described with the integration branch (Branch to merge to) configured to "developAutoMerge" and leaved the 'branch' field in the Git SCM blank. When I "Build now" I get following exception: Fetching changes from the remote Git repository Fetching upstream changes from git@REPOSITORY.git Seen branch in repository origin/develop Seen branch in repository origin/developAutoMerge Seen branch in repository origin/feature/blabla [...] Seen branch in repository origin/master Seen branch in repository origin/release/2.6.1 Seen branch in repository origin/release/2.6.2 Seen 13 remote branches Multiple candidate revisions Scheduling another build to catch up with blaServerBuild_developAutoMerge Merging Revision 6474f8ef91822e58edc55aad707d2725ff5a8431 (origin/feature/blabla) onto /developAutoMerge using resolve strategy FATAL: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128: stdout: /developAutoMerge^{commit} stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions hudson.plugins.git.GitException: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128: stdout: /developAutoMerge^{commit} stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:947) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:401) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:62) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:795) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:862) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) I found a similar problem by googling: https://groups.google.com/forum/#!topic/jenkinsci-dev/ek4hYR-z08k The proposed solution there was downgrading the Jenkins Git plugin from 2.0 to 1.4.0.
    via by m r,
  • GitHub comment 1#273282461
    via GitHub by umihai1
    ,
  • commit notification null
    via GitHub by danalbu
    ,
  • Since on of our recent updates of the jenkins LTS version and all available plugins, git checkout sometimes fail with the following exception: FATAL: Could not checkout master with start point 94f70933316a337a21037ad791f6015ce7d561e5 hudson.plugins.git.GitException: Could not checkout master with start point 94f70933316a337a21037ad791f6015ce7d561e5 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:1090) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Result has multiple lines at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.firstLine(CliGitAPIImpl.java:422) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:354) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:255) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.parseBranches(CliGitAPIImpl.java:1024) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getBranches(CliGitAPIImpl.java:1035) at hudson.plugins.git.GitAPI.getBranches(GitAPI.java:153) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:1081) ... 16 more So ar this only happens in multi-configuration projects where we merge cchanges from a branch taht triggered the job back to the master branch. The error seems to occur randomly on one of the configurations, but not on the master job itself.
    via by Johannes Wienke,
  • We have a matrix project configured to merge a git feature branch onto the master before starting the build. The exact configuration is attached as screenshot. The documentation for the "Name of repository" oarameter of the "Merge before build" behavior states that: {quote} If left blank, it'll default to the name of the first repository configured above. {quote} However, when leaving this field empty, you receive the following output when triggering the build: {noformat} Started by an SCM change Building remotely on ubuntu_trusty_64bit (trusty gcc ubuntu-next java7 ubuntu linux 64bit) in workspace /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator selected Git installation does not exists. Using Default Wiping out workspace first. Cloning the remote Git repository Cloning repository https://code.cor-lab.org/git/rsb.git.cpp > git init /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git --version # timeout=10 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10 Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/0.10 Seen branch in repository origin/0.3 Seen branch in repository origin/0.4 Seen branch in repository origin/0.5 Seen branch in repository origin/0.6 Seen branch in repository origin/0.7 Seen branch in repository origin/0.9 Seen branch in repository origin/agni Seen branch in repository origin/bug-1285 Seen branch in repository origin/enhancement-1096 Seen branch in repository origin/enhancement-1757 Seen branch in repository origin/enhancement-2034 Seen branch in repository origin/master Seen branch in repository origin/wip-introspection Seen branch in repository origin/wip-rosetta Seen branch in repository origin/wip-static-participants Seen 16 remote branches Multiple candidate revisions Scheduling another build to catch up with rsb-cpp-trunk-merge-simulator Merging Revision 70a3fd1f2425cdc779d83314c6978955979e9237 (origin/enhancement-1757) onto /master using default strategy > git rev-parse /master^{commit} # timeout=10 FATAL: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128: stdout: /master^{commit} stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1413) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1112) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1122) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:518) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:309) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) {noformat}
    via by Johannes Wienke,
    • hudson.plugins.git.GitException: Command "git rev-parse origin/master^{commit}" returned status code 128: stdout: origin/master^{commit} stderr: fatal: ambiguous argument 'origin/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1752) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1725) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1721) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1391) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1403) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:685) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:316) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:64) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:994) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1083) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor2 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    2 more bugmates