[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Philip O'Gorman commented on JENKINS-59387 Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" Thanks Mark - the work around for us is to use ssh instead of http. I'm not really sure whats happening, all of our builds are done from a clean workspace, requiring a full clone. I can clone on the machine using http when I login as the jenkins user. This issue just came up when I updated the latest jenkins and git-client late last week (2.190.1 & 2.8.6). Either way using ssh has fixed the issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.8076.1569863760396%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Philip O'Gorman commented on JENKINS-59387 Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" Mark Waite apologies - I just realised they are not the same - I think the stack trace was similar though, here is the end of the console message: Resolving deltas: 97% (1034/1056) Resolving deltas: 98% (1036/1056) Resolving deltas: 99% (1054/1056) Resolving deltas: 100% (1056/1056) Resolving deltas: 100% (1056/1056), done. 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 org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Should I create a new issue? Add Comment This message was sent by Atlass
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title
Philip O'Gorman edited a comment on JENKINS-59387
Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
I'm seeing this error t0o too - I've disabled Windows Credential manager: {code:java}using credential ea2a4045-c112-445c-8b6c-57c20e5a8699Cloning the remote Git repositoryCloning with configured refspecs honoured and without tagsCloning repository https://myurl.git > git.exe init E:\wp\ler-multibranch-pipeline_develop # timeout=10Fetching upstream changes from https://myurl.git > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket login for jenkins > git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: remote: Counting objects: 1436, done.{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.7945.1569856380211%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title
Philip O'Gorman edited a comment on JENKINS-59387
Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
I'm seeing this error to t0o - I've disabled Windows Credential manager: {code:java}using credential ea2a4045-c112-445c-8b6c-57c20e5a8699Cloning the remote Git repositoryCloning with configured refspecs honoured and without tagsCloning repository https://myurl.git > git.exe init E:\wp\ler-multibranch-pipeline_develop # timeout=10Fetching upstream changes from https://myurl.git > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket login for jenkins > git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: remote: Counting objects: 1436, done.{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.7935.1569856080198%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Philip O'Gorman commented on JENKINS-59387 Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" I'm seeing this error to - I've disabled Windows Credential manager: using credential ea2a4045-c112-445c-8b6c-57c20e5a8699 Cloning the remote Git repository Cloning with configured refspecs honoured and without tags Cloning repository https://myurl.git > git.exe init E:\wp\ler-multibranch-pipeline_develop # timeout=10 Fetching upstream changes from https://myurl.git > git.exe --version # timeout=10 using GIT_ASKPASS to set credentials Bitbucket login for jenkins > git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git.exe fetch --no-tags --progress -- https://myurl.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Counting objects: 1436, done. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https
[JIRA] (JENKINS-53072) Artifacts can't be downloaded if there is a + in the filename
Title: Message Title Philip O'Gorman created an issue Jenkins / JENKINS-53072 Artifacts can't be downloaded if there is a + in the filename Issue Type: Bug Assignee: Sean Turner Attachments: artifact1.PNG, artifact2.PNG Components: artifactdeployer-plugin Created: 2018-08-16 15:54 Environment: Jenkins 2.107.3 Labels: artifact-download artifact artefact Priority: Major Reporter: Philip O'Gorman We started to use the semantic versioning on our builds, artifacts now have a + in the file name, but now cannot be downloaded Add Comment
[JIRA] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Philip O'Gorman commented on JENKINS-30744 Re: multibranch issues if branch contains / I couldn't figure this out either. If we use gitflow - we have to make sure that we don't use the default branch names: feature/myfeat bug/themess I don't know why this issue is marked as closed? What are we missing here? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41935) Publish to dropbox fails
Title: Message Title Philip O'Gorman commented on JENKINS-41935 Re: Publish to dropbox fails I changed the credentials again this evening and it started to work again. Thanks for your help! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41935) Publish to dropbox fails
Title: Message Title Philip O'Gorman commented on JENKINS-41935 Re: Publish to dropbox fails Travis Donia Did it suddenly stop working for you recently? We had been using it for months without issue, no jenkins or server changes that I know of, then it stopped working. Could be on the dropbox end? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41935) Publish to dropbox fails
Title: Message Title Philip O'Gorman commented on JENKINS-41935 Re: Publish to dropbox fails Hi Rene, I tried another dropbox account and apikey, but I got the same issue. The test works fine but the jobs have the same failure. If I add a incorrect folder name the test will fail, when I add the correct folder name the test passed. So i believe that the credentials and connectivity are fine. I'm a newbie to Jenkins, where should I be looking for the logs? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41935) Publish to dropbox fails
Title: Message Title
Philip O'Gorman created an issue
Jenkins / JENKINS-41935
Publish to dropbox fails
Issue Type:
Bug
Assignee:
René de Groot
Components:
publish-over-dropbox-plugin
Created:
2017/Feb/10 4:52 PM
Environment:
ver 1.1.2, Windows, Jenkins ver. 2.32.1,
Priority:
Blocker
Reporter:
Philip O'Gorman
The publish suddenly stopped working: {{Dropbox:Connecting from host [JCAEIC-WSVR01] Dropbox:Connecting with configuration [Default] ... Dropbox:Caught exception [Exception when disconnecting from server. Message Failed to open connection to server] Sleeping for [2,000]ms before trying again Dropbox:Connecting with configuration [Default] ... Dropbox:Caught exception [Exception when disconnecting from server. Message Failed to open connection to server] Sleeping for [2,000]ms before trying again Dropbox:Connecting with configuration [Default] ... Dropbox:Caught exception [Exception when disconnecting from server. Message Failed to open connection to server] Sleeping for [2,000]ms before trying again Dropbox:Connecting with configuration [Default] ...}} The "Test Configuration" button always returns success, but none of the build jobs can publish
