| 636 |
mateusz.vi |
1 |
|
|
|
2 |
|
|
|
3 |
BUILD SERVER SETUP
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
=== INTRO =====================================================================
|
|
|
8 |
|
|
|
9 |
The SvarDOS build system is entirely stored in the project's svn repository.
|
|
|
10 |
This includes many components:
|
|
|
11 |
|
|
|
12 |
- SvarDOS-specific tools (install, pkg, pkgnet, localcfg, svarcom, help, ...)
|
|
|
13 |
- SvarDOS packages
|
|
|
14 |
- SvarDOS website
|
|
|
15 |
- build scripts and tools
|
|
|
16 |
|
|
|
17 |
This means that the project's svn tree contains everything that is required
|
|
|
18 |
to build SvarDOS.
|
|
|
19 |
|
|
|
20 |
|
|
|
21 |
=== SVN SERVICE ===============================================================
|
|
|
22 |
|
|
|
23 |
The server must have a subversion service installed with the SvarDOS repository
|
|
|
24 |
imported.
|
|
|
25 |
|
|
|
26 |
The only specific configuration concerns a post-commit hook that should be set
|
|
|
27 |
up to create a /tmp/svados_repo_changed.flag file whenever a commit is made to
|
|
|
28 |
the repo. Such hook script can be as simple as this:
|
|
|
29 |
|
|
|
30 |
echo date > /tmp/svardos_repo_changed.flag
|
|
|
31 |
exit 0
|
|
|
32 |
|
|
|
33 |
|
|
|
34 |
=== SVN CLIENT ================================================================
|
|
|
35 |
|
|
|
36 |
The SvarDOS repository should be checked out in /srv/svardos/:
|
|
|
37 |
|
|
|
38 |
$ svn co svn://127.0.0.1/svardos /srv/svardos
|
|
|
39 |
|
|
|
40 |
|
|
|
41 |
=== WEB SERVICE ===============================================================
|
|
|
42 |
|
|
|
43 |
A web server with PHP must be running (typically Apache). The PHP installation
|
|
|
44 |
needs the php-zip extension (required by buildidx), and the Apache web root
|
|
|
45 |
should point at /srv/svardos/website.
|
|
|
46 |
|
|
|
47 |
|
|
|
48 |
=== CRON ACTIONS ==============================================================
|
|
|
49 |
|
|
|
50 |
A cron job should be configured to run frequently (like every minute) and
|
|
|
51 |
execute the /srv/svardos/cron.sh script. This script is responsible for
|
|
|
52 |
checking out the local svardos repo whenever a new commit is being made, and
|
|
|
53 |
rebuilds the index of the packages repository.
|
|
|
54 |
|
|
|
55 |
|
|
|
56 |
=== MIRRORING THE PROJECT'S SVN ===============================================
|
|
|
57 |
|
|
|
58 |
Mirroring the project's svn tree (containing all build scripts, packages, etc)
|
|
|
59 |
is the best way to make a backup copy of the entire SvarDOS build system along
|
|
|
60 |
with all its history. To achieve such mirror, one needs to create an empty
|
|
|
61 |
svn repository and populate it using svnsync:
|
|
|
62 |
|
|
|
63 |
$ svnadmin create /srv/svardos-mirror
|
|
|
64 |
$ svnsync init file:///srv/svardos-mirror svn://svn.svardos.org/svardos
|
|
|
65 |
$ svn up /srv/svardos-mirror
|
|
|
66 |
|
|
|
67 |
The same procedure can be used to migrate the SvarDOS build system from one
|
|
|
68 |
server to another.
|
|
|
69 |
|
|
|
70 |
NOTE: The target svn server must allow modification of revision properties.
|
|
|
71 |
This is achieved with a svn "pre-revprop-change" hook of two lines:
|
|
|
72 |
#!/bin/sh
|
|
|
73 |
exit 0
|
|
|
74 |
|
|
|
75 |
|
|
|
76 |
======================================================================= EOF ===
|