Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: git-automerger-plugin, git-plugin
-
Environment:jenkins-2.194
-
Similar Issues:
Description
When I I copy my Private project link to Jenkins, I get some error like this:
Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h -- https://github.sydney.edu.au/SOFT2412-2019S2/WBYWJD_WYWJD_Team15.git HEAD" returned status code 128: stdout: stderr: Logon failed, use ctrl+c to cancel basic credential prompt. error: cannot spawn C:\WINDOWS\TEMP\pass6522988368209337473.bat: No error fatal: could not read Username for 'https://github.sydney.edu.au': terminal prompts disabled
And when I try to build something there, the log of Confirmation failure is like that.
Started by GitHub push by zzho0631 Running as SYSTEM Building in workspace C:\Program Files (x86)\Jenkins\workspace\Team15 using credential ec3b9de9-638a-472d-a137-668b7c1744f8 Cloning the remote Git repository Cloning repository https://github.sydney.edu.au/SOFT2412-2019S2/WBYWJD_WYWJD_Team15.git > git.exe init C:\Program Files (x86)\Jenkins\workspace\Team15 # timeout=10 Fetching upstream changes from https://github.sydney.edu.au/SOFT2412-2019S2/WBYWJD_WYWJD_Team15.git > git.exe --version # timeout=10 using GIT_ASKPASS to set credentials > git.exe fetch --tags --force --progress -- https://github.sydney.edu.au/SOFT2412-2019S2/WBYWJD_WYWJD_Team15.git +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git.exe fetch --tags --force --progress -- https://github.sydney.edu.au/SOFT2412-2019S2/WBYWJD_WYWJD_Team15.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: Logon failed, use ctrl+c to cancel basic credential prompt. error: cannot spawn C:\WINDOWS\TEMP\pass2346010482442283795.bat: No error fatal: could not read Username for 'https://github.sydney.edu.au': terminal prompts disabled at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) ERROR: Error cloning remote repo 'origin' Finished: FAILURE
Philip O'Gorman the message you're reporting is not the same message as the message that is reported here. The text in your message:
indicates that command line git successfully authenticated to the remote git server, requested data, and received data. The reason for the failure is not clear in the log output you included, but it is sufficient to show that initial authentication and initial connection are not the issue you are seeing.
I suspect a configuration issue in your case, or an issue that your remote git server has chosen to close the connection after the authentication was successful and data was transferred.
The original message reported in this bug report was not able to authenticate to the remote server.