hudson.plugins.git.GitException: Command "/usr/local/git/bin/git checkout -b ${DATA_DEPLOY_BRANCH} e60ebf368ec03b4e4dd449427d50115203049218" returned status code 128: stdout: stderr: fatal: A branch named 'mybranch' already exists.

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 Jenkins JIRA by b2jrock, 1 year ago
Command "/usr/local/git/bin/git checkout -b ${DATA_DEPLOY_BRANCH} e60ebf368ec03b4e4dd449427d50115203049218" returned status code 128: stdout: stderr: fatal: A branch named 'mybranch' already exists.
via Jenkins JIRA by b2jrock, 1 year ago
Command "/usr/local/git/bin/git checkout -b ${DATA_DEPLOY_BRANCH} e60ebf368ec03b4e4dd449427d50115203049218" returned status code 128: stdout: stderr: fatal: A branch named 'mybranch' already exists.
via Jenkins JIRA by Karl Ostmo, 1 year ago
Command "git fetch -t origin +refs/heads/*:refs/remotes/origin/*" returned status code 1: stdout: stderr: error: unable to resolve reference refs/remotes/origin/foo/bar/blah: Not a directory From ssh://stash.teslamotors.com:7999/FW/firmware ! [new
via Jenkins JIRA by Karl Ostmo, 1 year ago
Command "git fetch -t origin +refs/heads/*:refs/remotes/origin/*" returned status code 1: stdout: stderr: error: unable to resolve reference refs/remotes/origin/foo/bar/blah: Not a directory From ssh://stash.teslamotors.com:7999/FW/firmware ! [new
via Jenkins JIRA by m r, 1 year ago
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
via Jenkins JIRA by Sampo Niskanen, 1 year ago
Command "git fetch -t origin +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: ssh: Could not resolve hostname bitbucket.org: Temporary failure in name resolution fatal: The remote end hung up unexpectedly
hudson.plugins.git.GitException: Command "/usr/local/git/bin/git checkout -b ${DATA_DEPLOY_BRANCH} e60ebf368ec03b4e4dd449427d50115203049218" returned status code 128: stdout: stderr: fatal: A branch named 'mybranch' already exists.
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:748)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkout(CliGitAPIImpl.java:845)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1283)
at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232)
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:1145)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Thread.java:722)

Users with the same issue

Once, 2 weeks 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

Write tip

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