[ 
https://issues.jenkins-ci.org/browse/JENKINS-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Clarke resolved JENKINS-4687.
-------------------------------------

    Fix Version/s: current
       Resolution: Fixed

SSH has been re-enabled in version 2.1 and the GUI provides inputs for public 
key and password authentication in job setup
                
> Enhance CVS + SSH GUI
> ---------------------
>
>                 Key: JENKINS-4687
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-4687
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: cvs
>    Affects Versions: current
>         Environment: Platform: PC, OS: Linux
>            Reporter: lucianamssouza
>            Assignee: Michael Clarke
>             Fix For: current
>
>
> Hello,
> I installed Hudson in a debian machine and configured a project with SVN over
> SSH. This worked like a charm and I had my project in less than 5 minutes.
> When I tried to get the same working with CVS + SSH my problems started. 
> Apparently hudson is installed as a service in debian, which runs with the
> hudson user. I tried to configure the .ssh folder in this user's home 
> directory
> and add the required keys there to fetch the source from CVS. This got me a 
> bit
> further but then the keys needed to be unlocked. I thought of using ssh-agent 
> to
> unlock it, but I had no information on the hudson's user password (if there 
> is one).
> At this point I quit this approach killed the process and started it with the
> following command line under my user account:
> java -jar /usr/share/hudson/hudson.war
> With my user account as owner of the process the ssh keys are available and
> everything works fine.
> I suppose there is a better way of doing this but I could not find it. Maybe a
> similar approach as we have already for SVN over ssh would be ideal.
> Thx and best regards,
> Luciana Moreira

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
  • [JIRA] (JENKINS-4687) Enhance... michael.m.cla...@gmail.com (JIRA)

Reply via email to