[JIRA] (JENKINS-28165) git authentication with username/password over ssh fails - status code 128

2017-01-26 Thread cea...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Eagan commented on  JENKINS-28165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git authentication with username/password over ssh fails - status code 128   
 

  
 
 
 
 

 
 I'm seeing this same problem with Jenkins using SSH username/password authentication. In my case, I have a credential in the credential store with the username and password, but no matter what I do, I can't seem to get the fetch to work. Optimally, Jenkins would read the username and password from the credential store and use them to connect, but it seems to still be defaulting to the username on the system. If I force the username to be the one in the credential store by changing the URL to the git repository in Jenkins, it still fails to perform the checkout. I haven't found a method to get more details than those already provided in this bug report. Does anyone know how I can get more debug output?  
 

  
 
 
 
 

 
 
 

 
 
 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-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded

2013-01-03 Thread cea...@gmail.com (JIRA) 














































Chris Eagan
 commented on  JENKINS-12124


random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded















This happens for me now with the FindBugs 4.45 Plug-in and Jenkins 1.496. I downgraded the FindBugs Plug-in to 4.42 and everything works again.



























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