How do I use SVN+SSH with a custom port and externals on Jenkins

AlastairG

3/1/24, 2:04 PM

We use SVN with SSH because it is better than anonymous access and the HTTP setup looked complicated and difficult to use when I was setting up authenticated SVN.

Subversion uses a custom port because it is running in a docker image and we use the default SSH port for SSH access to the host.

We use the .ssh/config file to automatically select the correct port.

As a result, all our SVN externals do not specify the port number. Maybe they should. I don’t know, but it will be a huge amount of work to change them.

The result is that when I configure a job, which has externals because they all do, I can specify a port number in the top level SVN URL, but that doesn’t help me because checking out all the externals fails.

I tried setting the SVN_SSH environment variable, but maybe I need to reload Jenkins or something because it doesn’t seem to help at all.

If I create /home/jenkins/.ssh/config on the docker image, will that solve the problem? Will the Jenkins Subversion plugin pick it up? Or does it need to be in /var/lib/jenkins/.ssh/config?

0 + 0

ssh

svn

jenkins

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: How do I use SVN+SSH with a custom port and externals on Jenkins

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.