On Tue, Jan 19, 2021 at 5:03 AM Daniel Sahlberg
<daniel.l.sahlberg_at_gmail.com> wrote:
>
> Den tis 19 jan. 2021 kl 10:47 skrev David Aldrich <david.aldrich.ntml_at_gmail.com>:
>>
>> Hi
>>
>> We run a Jenkins job that lists the branches and tags of a certain svn repository by running 'svn ls'.
>>
>> The command, of course, requires svn authentication and so a password must be provided. Jenkins has a svn plugin which allows it to check out from svn repositories, using stored credentials, before running a job. As far as I know, the job itself can't access those credentials. The job script could provide the password but that is very insecure. I have gotten around this in the past by using gnome keyring, but I find that very hard to install on a headless server, so I have a problem of how to provide the password.
>>
>> So my question is: is it possible to authenticate to svn, i.e. run svn commands, using ssh key-based authentication instead of using a password?
>>
>> If so, can you point me in the right direction please?
>
>
> This is possible to tunnel the connection through SSH in which case you only need to authenticate the SSH connection (for example using keys). However it require some support/configuration on the server side so it depends on the server.
>
> The process is fairly well described in the Subversion book: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html
It does require some thought. It can be noticeably easier to support
than httpd and mod_dav based access, especially when a webserver is
already in place and doing a lot of production critical work.
Received on 2021-01-20 01:30:23 CET