We've seeing this error off and on since yesterday. It's causing our Jenkins builds to fail. It failed four times this morning, May 12, 2016, from 8:06 to 8:36 AM. There are at least two different errors:
> git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://bitbucket.org/xnatdev/xnat-data-models.git # timeout=10 Fetching upstream changes from https://bitbucket.org/xnatdev/xnat-data-models.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://bitbucket.org/xnatdev/xnat-data-models.git +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' ^[[8mha:AAAAWB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=^[[0mhudson.plugins.git.GitException: Failed to fetch from https://bitbucket.org/xnatdev/xnat-data-models.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://bitbucket.org/xnatdev/xnat-data-models.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1463) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:808) ... 11 more ERROR: null
And also:
> git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://bitbucket.org/xnatdev/xnat-data-models.git # timeout=10 Fetching upstream changes from https://bitbucket.org/xnatdev/xnat-data-models.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://bitbucket.org/xnatdev/xnat-data-models.git +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from https://bitbucket.org/xnatdev/xnat-data-models.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://bitbucket.org/xnatdev/xnat-data-models.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1463) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:808) ... 11 more ERROR: null
And then it worked suddenly at 8:41 AM:
> git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://bitbucket.org/xnatdev/xnat-data-models.git # timeout=10 Fetching upstream changes from https://bitbucket.org/xnatdev/xnat-data-models.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://bitbucket.org/xnatdev/xnat-data-models.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 9f72886ea2fac6aeda3755c84dffecd009494d89 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9f72886ea2fac6aeda3755c84dffecd009494d89 > git rev-list 16e6748cf54d8a24cb84dac8baae1e281ad4ff09 # timeout=10
We did nothing to our configuration or anything else in the meantime. It's affected multiple repos:
* https://bitbucket.org/rherrick/xnat-deploy.git
* https://bitbucket.org/xnatdev/spawner.git
* https://bitbucket.org/xnatdev/xnat-data-models.git
* https://bitbucket.org/xnatdev/xnat-deploy.git
* https://bitbucket.org/xnatdev/xnat-web.git
Let me know if I can get you any other info on our side.
Answers is a community Q&A site, but what you're describing sounds like an issue with the Bitbucket service. You might get some faster attention on this if you contact support@bitbucket.org
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems to be happening more frequently now as well. It's turning our build list red, which is not good.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.