hudson.plugins.git.GitException: Command "git rev-parse "origin/${gitlabTargetBranch}^{commit}"" returned status code 128: stdout: origin/${gitlabTargetBranch}^{commit} stderr: fatal: ambiguous argument 'origin/${gitlabTargetBranch}^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

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

,
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 GitHub by DoCode
, 1 year ago
Command "git rev-parse "origin/${gitlabTargetBranch}^{commit}"" returned status code 128: stdout: origin/${gitlabTargetBranch}^{commit} stderr: fatal: ambiguous argument 'origin/${gitlabTargetBranch}^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
via Google Groups by mdupont@caltesting.org (JIRA), 1 year ago
path not in the working tree. Use '--' to separate paths from revisions, like <span class="code-keyword" style="color: #000091">this</span>: 'git &lt;command&gt; [&lt;revision&gt;...] -- [&lt;file&gt;...]'
via Google Groups by mikhail@hotger.com (JIRA), 1 year ago
Command <span class="code-quote" style="color: #009100">&quot;/usr/bin/git rev-parse 2990ad0d3772^{commit}&quot;</span> returned status code 128: stdout: 2990ad0d3772^{commit} stderr: fatal: ambiguous argument '2990ad0d3772^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions
via GitHub by alex131290
, 1 year ago
}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
via jenkins-ci.org by Unknown author, 6 months ago
Command "git rev-parse origin/pr/220/merge^{commit}" returned status code 128: stdout: origin/pr/220/merge^{commit} stderr: fatal: ambiguous argument 'origin/pr/220/merge^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions
via Stack Overflow by user3502786
, 5 months ago
'bc19bbe50001d6e62a200933308458113b367498^{commit}': unknown revision or path not in the working tree. 16:44:30 Use '--' to separate paths from revisions, like this: 16:44:30 'git <command> [<revision>...] -- [<file>...]' 16:44:30
hudson.plugins.git.GitException: Command "git rev-parse "origin/${gitlabTargetBranch}^{commit}"" returned status code 128: stdout: origin/${gitlabTargetBranch}^{commit} stderr: fatal: ambiguous argument 'origin/${gitlabTargetBranch}^{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:1739)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1712)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1708)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1378)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1390)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:679)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:884)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:859)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:818)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:85)
at java.lang.Thread.run(Unknown Source)

Users with the same issue

Once, 1 week ago
Samebug visitor profile picture
Unknown user
Once, 2 months 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
4 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.