Subversion Repositories SvarDOS

                             BUILD SERVER SETUP

                             BUILD SERVER SETUP

=== INTRO =====================================================================

=== INTRO =====================================================================

The SvarDOS build system is entirely stored in the project's svn repository.

The SvarDOS build system is entirely stored in the project's svn repository.

This includes many components:

This includes many components:

 - SvarDOS-specific tools (install, pkg, pkgnet, localcfg, svarcom, help, ...)

 - SvarDOS-specific tools (install, pkg, pkgnet, localcfg, svarcom, help, ...)

 - SvarDOS packages

 - SvarDOS packages

 - SvarDOS website

 - SvarDOS website

 - build scripts and tools

 - build scripts and tools

This means that the project's svn tree contains everything that is required

This means that the project's svn tree contains everything that is required

to build SvarDOS.

to build SvarDOS.

=== SVN SERVICE ===============================================================

=== SVN SERVICE ===============================================================

The server must have a subversion service installed with the SvarDOS repository

The server must have a subversion service installed with the SvarDOS repository

imported.

imported.

The only specific configuration concerns a post-commit hook that creates a flag

The only specific configuration concerns a post-commit hook that creates a flag

file at /tmp/svados_repo_changed.flag whenever a commit is made to the repo and

file at /tmp/svados_repo_changed.flag whenever a commit is made to the repo and

another flag in /tmp/svardos_rebuilt_please.flag if the commit might impact the

another flag in /tmp/svardos_rebuilt_please.flag if the commit might impact the

content of installation images. Here below is the necessary post-commit hook,

content of installation images. Here below is the necessary post-commit hook,

it should be placed in the hooks/ directory of the svn server and made

it should be placed in the hooks/ directory of the svn server and made

executable (chmod +x):

executable (chmod +x):

#!/bin/sh

#!/bin/sh

SVNLOOK=/usr/bin/svnlook

SVNLOOK=/usr/bin/svnlook

REPOS="$1"

REPOS="$1"

REV="$2"

REV="$2"

# first of all, make sure to set a flag that says "svn content changed" so a

# first of all, make sure to set a flag that says "svn content changed" so a

# cron job can update its local copy later

# cron job can update its local copy later

echo `date` > /tmp/svardos_repo_changed.flag

echo `date` > /tmp/svardos_repo_changed.flag

# check if any of the following locations have been updated during the commit:

# check if any of the following locations have been updated during the commit:

#  - files

#  - files

#  - packages/core/

#  - packages/core/

#  - build.sh

#  - build.sh

#

#

# any change to one of these locations means that the content of the

# any change to one of these locations means that the content of the

# installation images may have been impacted, hence a rebuild may be necessary.

# installation images may have been impacted, hence a rebuild may be necessary.

#

#

$SVNLOOK changed -r "$REV" "$REPOS" | grep -e ' files' -e ' build.sh' -e ' packages/core/' > /dev/null

$SVNLOOK changed -r "$REV" "$REPOS" | grep -e ' files' -e ' build.sh' -e ' packages/core/' > /dev/null

# if a location matched, then set a flag so a cron job rebuilds the images

# if a location matched, then set a flag so a cron job rebuilds the images

# and send an information message back to the committer.

# and send an information message back to the committer.

if [ $? -eq 0 ] ; then

if [ $? -eq 0 ] ; then

  echo `date` > /tmp/svardos_rebuild_please.flag

  echo `date` > /tmp/svardos_rebuild_please.flag

  echo "NOTICE: a build-impacting location has been updated." >&2

  echo "NOTICE: a build-impacting location has been updated." >&2

  echo "        install images have been scheduled for a rebuild." >&2

  echo "        install images have been scheduled for a rebuild." >&2

  exit 1

  exit 1

fi

fi

exit 0

exit 0

=== SVN CLIENT ================================================================

=== SVN CLIENT ================================================================

The SvarDOS repository should be checked out in /srv/svardos/:

The SvarDOS repository should be checked out in /srv/svardos/:

$ svn co svn://127.0.0.1/svardos /srv/svardos

$ svn co svn://127.0.0.1/svardos /srv/svardos

=== WEB SERVICE ===============================================================

=== WEB SERVICE ===============================================================

A web server with PHP must be running (typically Apache). The PHP installation

A web server with PHP must be running (typically Apache). The PHP installation

needs the php-zip extension (required by buildidx), and the Apache web root

needs the php-zip extension (required by buildidx), and the Apache web root

should point at /srv/svardos/website.

should point at /srv/svardos/website.

=== CRON ACTIONS ==============================================================

=== CRON ACTIONS ==============================================================

A cron job should be configured to run frequently (like every minute) and

A cron job should be configured to run frequently (like every minute) and

execute the /srv/svardos/cron.sh script. This script is responsible for

execute the /srv/svardos/cron.sh script. This script is responsible for

checking out the local svardos repo whenever a new commit is being made, and

checking out the local svardos repo whenever a new commit is being made, and

=== MIRRORING THE PROJECT'S SVN ===============================================

=== MIRRORING THE PROJECT'S SVN ===============================================

Mirroring the project's svn tree (containing all build scripts, packages, etc)

Mirroring the project's svn tree (containing all build scripts, packages, etc)

is the best way to make a backup copy of the entire SvarDOS build system along

is the best way to make a backup copy of the entire SvarDOS build system along

with all its history. To achieve such mirror, one needs to create an empty

with all its history. To achieve such mirror, one needs to create an empty

svn repository and populate it using svnsync:

svn repository and populate it using svnsync:

$ svnadmin create /srv/svardos-mirror

$ svnadmin create /srv/svardos-mirror

$ svnsync init file:///srv/svardos-mirror svn://svn.svardos.org/svardos

$ svnsync init file:///srv/svardos-mirror svn://svn.svardos.org/svardos

$ svn up /srv/svardos-mirror

$ svn up /srv/svardos-mirror

The same procedure can be used to migrate the SvarDOS build system from one

The same procedure can be used to migrate the SvarDOS build system from one

server to another.

server to another.

NOTE: The target svn server must allow modification of revision properties.

NOTE: The target svn server must allow modification of revision properties.

      This is achieved with a svn "pre-revprop-change" hook of two lines:

      This is achieved with a svn "pre-revprop-change" hook of two lines:

        #!/bin/sh

        #!/bin/sh

        exit 0

        exit 0

======================================================================= EOF ===

======================================================================= EOF ===