Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via jenkins-ci.org by Unknown author

    Our Jenkins(J) is linked with Bitbucket(BB). A pull request(PR) is created in BB, then it's auto-built in J, then it's updated with a commit but BB doesn't update the branch, so J can't check it out. Solution: open the PR in BB web ui.

Solutions on the web

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>...]'
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>...]'
via Stack Overflow by dave
, 5 months ago
Command "git rev-parse 8b173b71e025^{commit}" returned status code 128: stdout: 8b173b71e025^{commit} stderr: fatal: ambiguous argument '8b173b71e025^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
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
via Jenkins JIRA by Matt Evans, 1 year 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
via GitHub by phaza
, 7 months ago
}': unknown revision or path not in the working tree. 00:00:12.964 Use '--' to separate paths from revisions, like this: 00:00:12.964 'git <command> [<revision>...] -- [<file>...]' 00:00:12.964
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)