Installing and Configuring an SVN Server with Jenkins Integration on Docker

1. Installation

Install Subversion on the Docker host:

yum -y install subversion

Create the repository directory and initialize it:

mkdir -pv /data/svn

svnadmin create /data/svn

Navigate to the repository and list its contents to verify the structure:

cd /data/svn/

ll

2. Configuration

Edit the password file:

cd conf/

vim passwd

View the authorization file without comments:

egrep -v '^#|^$' authz

Typical authz content:

[aliases]

[groups]

[/]

hahashen = rw

Edit svnserve.conf to set access rules:

vim svnserve.conf

egrep -v '^#|^$' svnserve.conf

Key settings:

anon-access = read

auth-access = write

password-db = passwd

authz-db = authz

Start the SVN server and verify it is listening:

svnserve -d -r /data/svn/

netstat -nltp

3. Testing SVN Operations

Create a working directory and check out the repository:

mkdir /soft

svn checkout svn://192.168.20.16 /soft/

Add a test file and commit it:

echo "123" >1.txt

svn add *

svn commit -m hahashen

4. Jenkins + SVN Integration

Create a new Jenkins job that pulls files from the SVN server.

In the job configuration, select “Send files or execute commands over SSH”.

View the files that Jenkins will distribute to the target host.

After building the job, verify that the target machine (e.g., 192.168.20.42) received the files.

Additional screenshots show the build process and final verification steps.

Finally, confirm that the remote host has received the dispatched files: