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>...]'


Solutions on the web516

Solution icon of jenkins
via Jenkins JIRA by Johannes Wienke, 1 year ago
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>...]'

Solution icon of jenkins
via Jenkins JIRA by Johannes Wienke, 1 year ago
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>...]'

Solution icon of jenkins
via Jenkins JIRA by Matt Evans, 1 year ago
Command "/usr/bin/git rev-parse /develop^{commit}" returned status code 128: stdout: /develop^{commit} stderr: fatal: ambiguous argument '/develop^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

Solution icon of jenkins
via Jenkins JIRA by Matt Evans, 10 months ago
Command "/usr/bin/git rev-parse /develop^{commit}" returned status code 128: 11:24:42 stdout: /develop^{commit} 11:24:42 11:24:42 stderr: fatal: ambiguous argument '/develop^{commit}': unknown revision or path not in the working tree. 11:24:42 Use '--' to separate paths from revisions 11:24:42

Solution icon of github
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

Solution icon of github
}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

Solution icon of github
}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

Solution icon of github
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>...]'

Solution icon of github
via GitHub by umihai1
, 9 months ago
Command "git.exe rev-parse "test1/master^{commit}"" returned status code 128: stdout: test1/master^{commit} stderr: fatal: ambiguous argument 'test1/master^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

Solution icon of jenkins
via Jenkins JIRA by Russ Kubik, 1 year ago
Command "git rev-list master" returned status code 128: stdout: stderr: fatal: ambiguous argument 'master': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

Stack trace

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)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 month ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
2 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
3 more bugmates