com.google.common.util.concurrent.UncheckedExecutionException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git failed with code 128. Working directory was [.]., stderr: [fatal: https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git/info/refs not found: did you run git update-server-info on the server?]

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

Solutions on the web

via Atlassian JIRA by David Rizzuto [Atlassian], 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git failed with code 128. Working directory was [.]., stderr: [fatal: https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git/info/refs not found: did you run git update-server-info on the server?]
via Atlassian JIRA by David Rizzuto [Atlassian], 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git failed with code 128. Working directory was [.]., stderr: [fatal: https://mrdon:********@bitbucket.org/atlassian/remotable-plugins.git/info/refs not found: did you run git update-server-info on the server?]
via Atlassian JIRA by Supriya Supugade, 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://s391679:********@scm.principal.com/projects/CSSMIGR/repos/ failed with code 128. Working directory was [.]., stderr: [fatal: https://s391679:********@scm.principal.com/projects/CSSMIGR/repos/info/refs not valid: is this a git repository?]
via Atlassian JIRA by Supriya Supugade, 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://s391679:********@scm.principal.com/projects/CSSMIGR/repos/ failed with code 128. Working directory was [.]., stderr: [fatal: https://s391679:********@scm.principal.com/projects/CSSMIGR/repos/info/refs not valid: is this a git repository?]
via Atlassian JIRA by Martin Meinhold, 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://melias@bitbucket.org/atlassian-foundation/codefoundation failed with code 128. Working directory was [.]., stderr: [fatal: https://melias@bitbucket.org/atlassian-foundation/codefoundation/info/refs not found: did you run git update-server-info on the server?]
via Atlassian JIRA by Martin Meinhold, 1 year ago
com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://melias@bitbucket.org/atlassian-foundation/codefoundation failed with code 128. Working directory was [.]., stderr: [fatal: https://melias@bitbucket.org/atlassian-foundation/codefoundation/info/refs not found: did you run git update-server-info on the server?]
com.atlassian.utils.process.ProcessException: Non-zero exit code: 128
at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:69)
at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(ExternalProcessImpl.java:556)
at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:472)
at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:426)
at com.atlassian.bamboo.plugins.git.GitCommandProcessor.runCommand(GitCommandProcessor.java:423)
at com.atlassian.bamboo.plugins.git.GitCommandProcessor.getRemoteRefs(GitCommandProcessor.java:351)
at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper$1.call(NativeGitOperationHelper.java:473)
at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper$1.call(NativeGitOperationHelper.java:464)
at com.atlassian.bamboo.plugins.git.CallableResultCache$1.load(CallableResultCache.java:29)
at com.atlassian.bamboo.plugins.git.CallableResultCache$1.load(CallableResultCache.java:25)
at com.google.common.cache.CustomConcurrentHashMap$ComputingValueReference.compute(CustomConcurrentHashMap.java:3426)
at com.google.common.cache.CustomConcurrentHashMap$Segment.compute(CustomConcurrentHashMap.java:2322)
at com.google.common.cache.CustomConcurrentHashMap$Segment.getOrCompute(CustomConcurrentHashMap.java:2291)
at com.google.common.cache.CustomConcurrentHashMap.getOrCompute(CustomConcurrentHashMap.java:3802)
at com.google.common.cache.ComputingCache.get(ComputingCache.java:46)
at com.atlassian.bamboo.plugins.git.CallableResultCache.call(CallableResultCache.java:82)
at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper.getRemoteRefs(NativeGitOperationHelper.java:485)
at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper.resolveBranch(NativeGitOperationHelper.java:420)
at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper.obtainLatestRevision(NativeGitOperationHelper.java:518)
at com.atlassian.bamboo.plugins.git.GitRepository.getLastCommit(GitRepository.java:522)
at com.atlassian.bamboo.plan.branch.BranchExpiryJob.execute(BranchExpiryJob.java:88)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at com.atlassian.bamboo.quartz.SystemAuthorizedThreadPool$1.run(SystemAuthorizedThreadPool.java:38)

Users with the same issue

You are the first who have seen this exception.

Write tip

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