[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-08-28 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 updated  JENKINS-21518


Error while using SSH credentials to fetch git repository.
















Change By:


Jesse Glick
(28/Aug/14 3:01 PM)




Labels:


authentication
,
gitssh
,



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-07-22 Thread m...@iflowfor8hours.info (JIRA)














































matt urbanski
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















I have seen this when a slave is using two sets of ssh credentials at the same time. In my case it was the ssh-agent plugin and the git plugin conflicting. As soon as I got rid of one of them, everything worked again. 
YMMV.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-03-18 Thread vikram.sesha...@gmail.com (JIRA)














































Meta Stable
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















I am currently running Jenkins 1.537, with the following plugins:
Credentials plugin: 1.9.4
SSH Credentials Plugin: 1.6
SSH Slaves Plugin: 1.5
Strictly speaking, I'm not sure any are required other than "SSH Credentials Plugin".

I see that new version(s) are available, both for Jenkins as well as some of these plugins, so I will update and check. But I am still facing this problem.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-03-18 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















The Credentials plugin is required with the git-plugin and the git-client-plugin.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-03-17 Thread d...@n-cube.org (JIRA)














































Dan Savilonis
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















I'm seeing the same behavior on 1.555 with up to date git plugins as of Mar 17. This was working fine and I kept hitting 'rebuild last', and suddenly I got this error. A regular build does not work either.

I was editing the job, so I expect that somehow introduced this. I've seen job configuration get corrupted in the past after repeated saves.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-03-14 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















Have you checked with the most recent versions of the git-client-plugin and the git-plugin?

I've not seen any issues with remoting failures using my collection of Debian Linux variants (7.1 x86, Testing x64, 7.1 x64) and Windows (Win 7 x86, Windows Home Server 2011 x86, Windows 8.1 x64).  They are all running Java 1.7.0_51 as provided by Oracle, though I don't expect any issues related to the provider of the JDK either.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-02-25 Thread lee...@gmail.com (JIRA)














































William Leese
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















Same issue, Linux master  linux slaves. Jenkins 1.540, but with the credentials and ssh-credentials plugins up to date.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.


[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-02-12 Thread hiroshi.w...@nicta.com.au (JIRA)












































 
Hiroshi Wada
 edited a comment on  JENKINS-21518


Error while using SSH credentials to fetch git repository.
















I've got the exactly same issue with the combination of Linux master (Jenkins 1.550 on Ubuntu 12.04) and Windows slave (slave.jar is up-to-date.) We manage private keys with Jenkins credentials plugin and directly paste keys on Jenkins console.

Strange thing is remote build succeeds after rebooting a master or a slave. However, after while, all remote builds start failing. Not exactly sure what triggers the failure but it seems to occur after running a project which uses a different key, or after one of Jenkins projects fails due to wrong key settings.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.


[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-02-12 Thread hiroshi.w...@nicta.com.au (JIRA)














































Hiroshi Wada
 commented on  JENKINS-21518


Error while using SSH credentials to fetch git repository.















I've got the exactly same issue with the combination of Linux master (Jenkins 1.550 on Ubuntu 12.04) and Windows slave (slave.jar is up-to-date.) We manage private keys with Jenkins credentials plugin and directly paste keys on Jenkins console.

Strange thing is remote build succeeds after rebooting a master or a slave. However, after while, all remote builds start failing. Not exactly sure what triggers the failure but it seems to occur after running a project which uses a different key, or after one of Jenkins projects fails due to wrong key settings.

(say, one of projects All build after the first one fail. Looks very strange.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.


[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-02-12 Thread hiroshi.w...@nicta.com.au (JIRA)












































 
Hiroshi Wada
 edited a comment on  JENKINS-21518


Error while using SSH credentials to fetch git repository.
















I've got the exactly same issue with the combination of Linux master (Jenkins 1.550 on Ubuntu 12.04) and Windows slave (slave.jar is up-to-date.) We manage private keys with Jenkins credentials plugin and directly paste keys on Jenkins console.

Strange thing is remote build succeeds after rebooting a master or a slave; however, after while, all remote builds start failing. Not exactly sure what triggers the failure but it seems to occur after running a project which uses a different key, or after one of Jenkins projects fails due to wrong key settings.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.


[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.

2014-01-27 Thread vikram.sesha...@gmail.com (JIRA)














































Meta Stable
 created  JENKINS-21518


Error while using SSH credentials to fetch git repository.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Attachments:


jenkins_bug.txt



Components:


git-client, ssh-credentials



Created:


27/Jan/14 2:57 PM



Description:


System is configured to use an SSH agent to get the build from the Git server, and build on the build agent. The system works intermittently, and when it doesn't, the error reported is:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Building remotely on Build Agent 1 in workspace C:\Jenkins\workspace\Fusion 3.69
FATAL: java.io.IOException: Remote call on Build Agent 1 failed
hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on Build Agent 1 failed
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:183)
	at com.sun.proxy.$Proxy75.addCredentials(Unknown Source)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl.addCredentials(RemoteGitImpl.java:196)
	at hudson.plugins.git.GitSCM.createClient(GitSCM.java:584)
	at hudson.plugins.git.GitSCM.createClient(GitSCM.java:561)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:866)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:230)
Caused by: java.io.IOException: Remote call on Build Agent 1 failed
	at hudson.remoting.Channel.call(Channel.java:723)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
	... 13 more
Caused by: java.lang.Error: Failed to deserialize the Callable object.
	at hudson.remoting.UserRequest.perform(UserRequest.java:104)
	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(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:58)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassCastException: cannot assign instance of com.cloudbees.plugins.credentials.CredentialsScope$2 to field com.cloudbees.plugins.credentials.BaseCredentials.scope of type com.cloudbees.plugins.credentials.CredentialsScope in instance of com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey
	at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(Unknown Source)
	at java.io.ObjectStreamClass.setObjFieldValues(Unknown Source)
	at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
	at java.io.ObjectInputStream.readSerialData(Unknown Source)
	at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
	at java.io.ObjectInputStream.readObject0(Unknown Source)
	at java.io.ObjectInputStream.readArray(Unknown Source)
	at java.io.ObjectInputStream.readObject0(Unknown Source)
	at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
	at java.io.ObjectInputStream.readSerialData(Unknown Source)
	at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
	at java.io.ObjectInputStream.readObject0(Unknown Source)
	at java.io.ObjectInputStream.readObject(Unknown Source)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	... 9 more

This seems similar to a few other