Recent changes to BuildServerSetup

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 10 Dec 2015 22:45:50 -0000

--- v10
+++ v11
@@ -108,6 +108,10 @@

 Install Git plugin 2.4.0 or later. Configure it to use the Git client you installed above.

+##### JaCoCo
+
+Install JaCoCo plugin 2.0.0 or later.
+
 ##### Xvfb

 Install Xvfb plugin 1.0.16 or later.  Xvfb is used to provide a virtual display on this headless server because some tests exercise the GUI.  The plugin does not automatically install Xvfb itself.  Therefore, If necessary, install [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) on the server prior to installing the plugin.

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 10 Dec 2015 22:44:47 -0000

--- v9
+++ v10
@@ -106,7 +106,7 @@

 ##### Git

-Install Git plugin 2.3.5 or later. Configure it to use the Git client you installed above.
+Install Git plugin 2.4.0 or later. Configure it to use the Git client you installed above.

 ##### Xvfb

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 10 Dec 2015 22:06:41 -0000

--- v8
+++ v9
@@ -33,7 +33,6 @@
 The Linux reference implementation uses the following operating system and system software:

   * CentOS 6.6 x86_64
-  * [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) (to provide a virtual display on this headless server)

 ## Build Tools

@@ -109,6 +108,10 @@

 Install Git plugin 2.3.5 or later. Configure it to use the Git client you installed above.

+##### Xvfb
+
+Install Xvfb plugin 1.0.16 or later.  Xvfb is used to provide a virtual display on this headless server because some tests exercise the GUI.  The plugin does not automatically install Xvfb itself.  Therefore, If necessary, install [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) on the server prior to installing the plugin.
+
 ## The Build User

 Create a dedicated, non-administrative user for hosting the build process. In the build user's home directory, create the following subdirectories:

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 10 Dec 2015 22:01:17 -0000

--- v7
+++ v8
@@ -15,7 +15,7 @@
 However, physical hardware is not necessary. In fact, it is recommended you use a [virtual machine](http://en.wikipedia.org/wiki/Virtual_machine) to host your build server. Several free virtualization solutions are available, including:

   * [Oracle VirtualBox](http://www.virtualbox.org/)
-  * [VMWare Player](http://www.vmware.com/products/player/overview.html)
+  * [VMware Player](http://www.vmware.com/products/player/overview.html)
   * [Xen](http://xen.org/)

 The Linux reference implementation uses Oracle VirtualBox 4.3 with the following virtual hardware:

BuildServerSetup modified by Steven Soloff

Steven Soloff — Sat, 12 Sep 2015 21:40:35 -0000

--- v6
+++ v7
@@ -95,11 +95,11 @@

 ##### Ant

-Add an Ant installation for Ant 1.9.2 to be installed automatically from Apache.
+Add an Ant installation for Ant 1.9.6 to be installed automatically from Apache.

 ##### Maven

-Add a Maven installation for Maven 3.1.1 to be installed automatically from Apache.
+Add a Maven installation for Maven 3.3.3 to be installed automatically from Apache.

 #### Plugins

BuildServerSetup modified by Steven Soloff

Steven Soloff — Wed, 09 Sep 2015 17:25:51 -0000

--- v5
+++ v6
@@ -124,7 +124,7 @@

 Several scripts are used to drive the build process. These scripts depend on your specific build environment and thus cannot be provided in a generalized form. The build team provides templates for these scripts in the version control repository. You must download these templates to your build server the first time you set it up. As the Build User, follow these steps to download the templates (~ refers to the build user's home directory):

-  1. Use the Git client to clone the repository that contains the build file templates: `git clone --depth=1 git://git.code.sf.net/p/gamegineer/build ~/build-workspace`
+  1. Use the Git client to clone the repository that contains the build file templates: `git clone --depth=1 git://github.com/gamegineer/build.git ~/build-workspace`
   1. Copy all the script templates in _~/build-workspace/scripts_ to _~/scripts_. 

 Now you must edit each of the script templates you copied. Using a text editor, open each of the script templates and supply appropriate values for the environment variables between the `BEGIN-CUSTOM-VARIABLES` and `END-CUSTOM-VARIABLES` markers.

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 30 Apr 2015 23:25:11 -0000

--- v4
+++ v5
@@ -124,20 +124,14 @@

 Several scripts are used to drive the build process. These scripts depend on your specific build environment and thus cannot be provided in a generalized form. The build team provides templates for these scripts in the version control repository. You must download these templates to your build server the first time you set it up. As the Build User, follow these steps to download the templates (~ refers to the build user's home directory):

-  1. Change to the directory _~/build-workspace_.
-  2. Use the Subversion client to download the root build files (note the period at the end of the command representing the current directory): `svn export --force http://svn.code.sf.net/p/gamegineer/code/build/trunk/ .`
-  3. Copy all the script templates in _~/build-workspace/scripts_ to _~/scripts_. 
-  4. Delete the contents of _~/build-workspace_ to ensure you have a pristine image before bootstrapping the build later.
+  1. Use the Git client to clone the repository that contains the build file templates: `git clone --depth=1 git://git.code.sf.net/p/gamegineer/build ~/build-workspace`
+  1. Copy all the script templates in _~/build-workspace/scripts_ to _~/scripts_. 

 Now you must edit each of the script templates you copied. Using a text editor, open each of the script templates and supply appropriate values for the environment variables between the `BEGIN-CUSTOM-VARIABLES` and `END-CUSTOM-VARIABLES` markers.

 If you are using a VM, you should save this image before continuing.

 The Linux reference implementation uses the directory names defined in the templates.
-
-## Bootstrap the Build Environment
-
-The first time you set up the build server (or any time you revert to the base build VM image created in the previous step), you must bootstrap the build environment. This is accomplished by running the _~/scripts/bootstrap-build-environment_ script. This script simply sets up the _~/build-workspace_ directory with the bootstrap files required by the build environment.

 ## Nexus

BuildServerSetup modified by Steven Soloff

Steven Soloff — Thu, 30 Apr 2015 23:08:17 -0000

--- v3
+++ v4
@@ -18,7 +18,7 @@
   * [VMWare Player](http://www.vmware.com/products/player/overview.html)
   * [Xen](http://xen.org/)

-The Linux reference implementation uses Oracle VirtualBox 4.2 with the following virtual hardware:
+The Linux reference implementation uses Oracle VirtualBox 4.3 with the following virtual hardware:

   * Intel Core i5-3570K single-core CPU @ 3.4 GHz
   * 1024 MB RAM
@@ -32,7 +32,7 @@

 The Linux reference implementation uses the following operating system and system software:

-  * CentOS 6.5 x86_64
+  * CentOS 6.6 x86_64
   * [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) (to provide a virtual display on this headless server)

 ## Build Tools
@@ -45,11 +45,11 @@

 The Linux reference implementation uses Oracle JRE 1.7.0_60 installed to _/home/build/tools/jre1.7.0_60_.

-### Subversion
+### Git

-Install version 1.6.x, 1.7.x, or 1.8.x of the [Subversion client](http://subversion.apache.org/). A Subversion client is required to bootstrap the build server from the Gamegineer version control repository.
+Install version 1.7.9 or later of the [Git client](http://git-scm.com/). A Git client is required to bootstrap the build server from the Gamegineer version control repository. It is also used by Jenkins to download the source for the various build jobs.

-The Linux reference implementation uses the _subversion_ RPM package version 1.6.11 installed to _/usr/bin_.
+The Linux reference implementation uses the _git_ RPM package version 1.7.12.4 from the _rpmforge-extras_ repository installed to _/usr/bin_.

 ### Nexus

@@ -67,35 +67,47 @@

 The Linux reference implementation uses Nexus OSS 2.6.2-01 installed to _/home/build/tools/nexus-2.6.2-01_.

-You must also install the Nexus plugins listed below.
+#### Plugins

-#### nexus-site-repository-plugin
+You must install the Nexus plugins listed below.
+
+##### nexus-site-repository-plugin

 Install version 2.6 or later of the Nexus site repository plugin. This plugin is used to host the project web sites generated using the Maven site goal. Refer to sections [18.5](http://books.sonatype.com/nexus-book/reference/_creating_a_site_repository.html) and [18.6](http://books.sonatype.com/nexus-book/reference/_add_the_site_deployment_role.html) of the Nexus book for installation instructions.

-#### unzip-repository-plugin
+##### unzip-repository-plugin

 Install version 0.12.0 or later of the Tycho Nexus unzip plugin. This plugin is used to publish zipped p2 update sites in a format the p2 director can consume. Refer to the [Tycho/Nexus Unzip Plugin](http://wiki.eclipse.org/Tycho/Nexus_Unzip_Plugin) wiki for installation instructions.

 ### Jenkins

-Install the latest version of [Jenkins](http://jenkins-ci.org/). Jenkins is the tool used to automate the build process.
+Install the latest long-term support (LTS) version of [Jenkins](http://jenkins-ci.org/). Jenkins is the tool used to automate the build process.

-The Linux reference implementation uses Jenkins 1.565 installed using the RPM package.
+The Linux reference implementation uses Jenkins LTS 1.596.2 installed using the RPM package.

-You must also configure Jenkins to use the following tools:
+#### Tools

-#### Java SE JDK
+You must configure Jenkins to use the following tools:
+
+##### Java SE JDK

 Add a JDK installation for Java SE Development Kit 7u51 to be installed automatically from java.sun.com.

-#### Ant
+##### Ant

 Add an Ant installation for Ant 1.9.2 to be installed automatically from Apache.

-#### Maven
+##### Maven

 Add a Maven installation for Maven 3.1.1 to be installed automatically from Apache.
+
+#### Plugins
+
+You must configure Jenkins to use the following plugins:
+
+##### Git
+
+Install Git plugin 2.3.5 or later. Configure it to use the Git client you installed above.

 ## The Build User

BuildServerSetup modified by Steven Soloff

Steven Soloff — Sat, 21 Jun 2014 01:19:45 -0000

--- v2
+++ v3
@@ -152,3 +152,5 @@
 ## Jenkins

 It is recommended to install Jenkins using the RPM package. This will configure Jenkins to automatically start when the server is started.
+
+The latest job configurations are stored in version control and can be found at _~/build-workspace/jenkins/jobs_.

BuildServerSetup modified by Steven Soloff

Steven Soloff — Sat, 21 Jun 2014 01:11:58 -0000

--- v1
+++ v2
@@ -4,220 +4,151 @@

 ## Overview

-This article describes how to set up a Gamegineer build server. Details of the team's reference implementation are provided throughout the article to assist you in easily understanding the build server requirements. 
+This article describes how to set up a Gamegineer build server. Details of the team's reference implementation are provided throughout the article to assist you in easily understanding the build server requirements.
+
+_At this time, the team only maintains a Linux build server reference implementation. The instructions in this article should be easily extendible to a Windows build server, but you may run into unforeseen issues not encountered on the Linux reference implementation. Please feel free to contribute instructions for setting up a Gamegineer build server on other platforms._

 ## Hardware

-It is preferable to have a dedicated machine as the build server. This will help you avoid corrupting your build environment with resources that exist outside of the version control repository. These external resources (e.g. different build tool versions, partially modified source code, etc.) have a tendency to make the build fail when it should pass and vice versa, resulting in much frustration. 
+It is preferable to have a dedicated machine as the build server. This will help you avoid corrupting your build environment with resources that exist outside of the version control repository. These external resources (e.g. different build tool versions, partially modified source code, etc.) have a tendency to make the build fail when it should pass and vice versa, resulting in much frustration.

-However, physical hardware is not necessary. In fact, it is recommended you use a [virtual machine](http://en.wikipedia.org/wiki/Virtual_machine) to host your build server. Several free virtualization solutions are available, including: 
+However, physical hardware is not necessary. In fact, it is recommended you use a [virtual machine](http://en.wikipedia.org/wiki/Virtual_machine) to host your build server. Several free virtualization solutions are available, including:

   * [Oracle VirtualBox](http://www.virtualbox.org/)
   * [VMWare Player](http://www.vmware.com/products/player/overview.html)
   * [Xen](http://xen.org/)

-The Windows reference implementation uses Oracle VirtualBox 4.2 with the following virtual hardware: 
+The Linux reference implementation uses Oracle VirtualBox 4.2 with the following virtual hardware:

-  * Intel Core i5-3570K single-core CPU @ 3.4 GHz 
-  * 512 MB RAM 
-  * 64 GB hard disk 
-  * DVD-ROM drive 
-  * Network adapter 
-
-The Linux reference implementation uses Oracle VirtualBox 4.2 with the following virtual hardware: 
-
-  * Intel Core i5-3570K single-core CPU @ 3.4 GHz 
-  * 1024 MB RAM 
-  * 128 GB hard disk 
-  * DVD-ROM drive 
-  * Network adapter 
+  * Intel Core i5-3570K single-core CPU @ 3.4 GHz
+  * 1024 MB RAM
+  * 128 GB hard disk
+  * DVD-ROM drive
+  * Network adapter

 ## Operating System

-Install a clean operating system and all available updates on your chosen hardware. Install any required system software, such as an antivirus package. If you are using a VM, you should save this image before continuing. 
+Install a clean operating system and all available updates on your chosen hardware. Install any required system software, such as an antivirus package. If you are using a VM, you should save this image before continuing.

-The Windows reference implementation uses the following operating system and system software: 
+The Linux reference implementation uses the following operating system and system software:

-  * Microsoft Windows XP Professional x86 with Service Pack 3 
-  * [ClamWin Free Antivirus](http://www.clamwin.com/)
-
-The Linux reference implementation uses the following operating system and system software: 
-
-  * CentOS 6.5 x86_64 
-  * [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) (to provide a virtual display on this headless server) 
+  * CentOS 6.5 x86_64
+  * [Xvfb](http://www.x.org/releases/X11R7.6/doc/man/man1/Xvfb.1.xhtml) (to provide a virtual display on this headless server)

 ## Build Tools

-Many of the build tools used by Gamegineer are not stored in version control simply due to the large size of their distributions. Therefore, it is necessary to install this software outside of the formal build process. As an administrative user, install the software packages that follow. Note that only specific versions have been approved for use on a Gamegineer build server; wildcards have been used where appropriate. 
+Many of the build tools used by Gamegineer are not stored in version control simply due to the large size of their distributions. Therefore, it is necessary to install this software outside of the formal build process. As an administrative user, install the software packages that follow. Note that only specific versions have been approved for use on a Gamegineer build server; wildcards have been used where appropriate.

-### Java SE JDK
+### Java SE JRE

-Install the latest update to version 1.6.0 of the [Java SE 6 JDK](http://www.oracle.com/technetwork/java/javase/overview/index.html). The Java SE 6 JDK is required to run CruiseControl, which is not compatible with Java SE 7. 
+Install the latest update to version 1.7.0 of the [Java SE 7 JRE](http://www.oracle.com/technetwork/java/javase/overview/index.html). The Java SE 7 JRE is required to run Nexus.

-Install the latest update to version 1.7.0 of the [Java SE 7 JDK](http://www.oracle.com/technetwork/java/javase/overview/index.html). The Java SE 7 JDK is required for most everything in the build process, including building and testing the software. 
-
-The Windows reference implementation uses Oracle JDK 1.6.0_45 installed to _C:\Program Files\Java\jdk1.6.0_45_ and Oracle JDK 1.7.0_51 installed to _C:\Program Files\Java\jdk1.7.0_51_. 
-
-The Linux reference implementation uses Oracle JDK 1.6.0_45 installed to _/home/build/tools/jdk1.6.0_45_ and Oracle JDK 1.7.0_51 installed to _/home/build/tools/jdk1.7.0_51_. 
-
-### Perl
-
-Install version 5.8.x or later of Perl. Perl is used to execute some build scripts. 
-
-The Windows reference implementation uses ActivePerl 5.16 installed to _C:\Perl_. 
-
-The Linux reference implementation uses the _perl_ yum package version 5.10 installed to _/usr/bin_. 
+The Linux reference implementation uses Oracle JRE 1.7.0_60 installed to _/home/build/tools/jre1.7.0_60_.

 ### Subversion

-Install version 1.6.x, 1.7.x, or 1.8.x of the [Subversion client](http://subversion.apache.org/). A Subversion client is required so the build server can download the latest sources from the Gamegineer version control repository. 
+Install version 1.6.x, 1.7.x, or 1.8.x of the [Subversion client](http://subversion.apache.org/). A Subversion client is required to bootstrap the build server from the Gamegineer version control repository.

-The Windows reference implementation uses Slik SVN 1.7.7 installed to _C:\Program Files\SlikSvn_. 
-
-The Linux reference implementation uses the _subversion_ yum package version 1.6.11 installed to _/usr/bin_ with a symbolic link to this directory at _/home/build/tools/svn_. 
-
-### Ant
-
-Install version 1.9.2 of [Apache Ant](http://ant.apache.org/). Ant is used to implement portions of the build process. 
-
-The Windows reference implementation uses Ant 1.9.2 installed to _C:\Program Files\apache-ant-1.9.2_. 
-
-The Linux reference implementation uses Ant 1.9.2 installed to _/home/build/tools/apache-ant-1.9.2_. 
-
-### Maven
-
-Install version 3.1.1 of [Apache Maven](http://maven.apache.org/). Maven is used to implement portions of the build process. 
-
-The Windows reference implementation uses Maven 3.1.1 installed to _C:\Program Files\apache-maven-3.1.1_. 
-
-The Linux reference implementation uses Maven 3.1.1 installed to _/home/build/tools/apache-maven-3.1.1_. 
+The Linux reference implementation uses the _subversion_ RPM package version 1.6.11 installed to _/usr/bin_.

 ### Nexus

-Install version 2.6.x of [Nexus](http://www.sonatype.org/nexus/). Nexus is used to manage build artifacts. 
+Install version 2.6.x of [Nexus](http://www.sonatype.org/nexus/). Nexus is used to manage build artifacts.

-The installation package will contain two directories. For example, _nexus-2.6.2-01_ (hereafter referred to as _nexus-home_) and _sonatype-work_. The contents of _nexus-home_ represent the actual application and should be copied to the appropriate installation directory (e.g. _~/tools/nexus-2.6.2-01_). The contents of _sonatype-work_ should be copied to _~/build-workspace/nexus_ (see below for the meaning of the _~/build-workspace/nexus_ directory). 
+The installation package will contain two directories. For example, _nexus-2.6.2-01_ (hereafter referred to as _nexus-home_) and _sonatype-work_. The contents of _nexus-home_ represent the actual application and should be copied to the appropriate installation directory (e.g. _~/tools/nexus-2.6.2-01_). The contents of _sonatype-work_ should be copied to _~/build-workspace/nexus_ (see below for the meaning of the _~/build-workspace/nexus_ directory).

-You must edit the _$nexus-home/conf/nexus.properties_ file, and change the value of the `nexus-work` property to the fully-qualified path to the _~/build-workspace/nexus_ directory. 
+You must edit the _$nexus-home/conf/nexus.properties_ file, and change the value of the `nexus-work` property to the fully-qualified path to the _~/build-workspace/nexus_ directory.

-To ensure Nexus does not fill up local storage with its artifacts, you must create several automated tasks that periodically remove old artifacts. Start Nexus and go to the **Administration > Scheduled Tasks** page. Create the following tasks: 
+To ensure Nexus does not fill up local storage with its artifacts, you must create several automated tasks that periodically remove old artifacts. Start Nexus and go to the **Administration > Scheduled Tasks** page. Create the following tasks:

-  * Remove Snapshots from Repository 
-  * Purge Nexus Timeline 
-  * Empty Trash 
+  * Remove Snapshots from Repository
+  * Purge Nexus Timeline
+  * Empty Trash

-The Windows reference implementation uses Nexus OSS 2.6.2-01 installed to _C:\Program Files\nexus-2.6.2-01_. 
+The Linux reference implementation uses Nexus OSS 2.6.2-01 installed to _/home/build/tools/nexus-2.6.2-01_.

-The Linux reference implementation uses Nexus OSS 2.6.2-01 installed to _/home/build/tools/nexus-2.6.2-01_. 
-
-You must also install the Nexus plugins listed below. 
+You must also install the Nexus plugins listed below.

 #### nexus-site-repository-plugin

-Install version 2.6 or later of the Nexus site repository plugin. This plugin is used to host the project web sites generated using the Maven site goal. Refer to sections [18.5](http://books.sonatype.com/nexus-book/reference/_creating_a_site_repository.html) and [18.6](http://books.sonatype.com/nexus-book/reference/_add_the_site_deployment_role.html) of the Nexus book for installation instructions. 
+Install version 2.6 or later of the Nexus site repository plugin. This plugin is used to host the project web sites generated using the Maven site goal. Refer to sections [18.5](http://books.sonatype.com/nexus-book/reference/_creating_a_site_repository.html) and [18.6](http://books.sonatype.com/nexus-book/reference/_add_the_site_deployment_role.html) of the Nexus book for installation instructions.

 #### unzip-repository-plugin

-Install version 0.12.0 or later of the Tycho Nexus unzip plugin. This plugin is used to publish zipped p2 update sites in a format the p2 director can consume. Refer to the [Tycho/Nexus Unzip Plugin](http://wiki.eclipse.org/Tycho/Nexus_Unzip_Plugin) wiki for installation instructions. 
+Install version 0.12.0 or later of the Tycho Nexus unzip plugin. This plugin is used to publish zipped p2 update sites in a format the p2 director can consume. Refer to the [Tycho/Nexus Unzip Plugin](http://wiki.eclipse.org/Tycho/Nexus_Unzip_Plugin) wiki for installation instructions.

-### CruiseControl
+### Jenkins

-Install version 2.8.x of [CruiseControl](http://cruisecontrol.sourceforge.net/). CruiseControl is the tool used to automate the build process. 
+Install the latest version of [Jenkins](http://jenkins-ci.org/). Jenkins is the tool used to automate the build process.

-The Windows reference implementation uses CruiseControl 2.8.4-bin installed to _C:\Program Files\cruisecontrol-2.8.4_. 
+The Linux reference implementation uses Jenkins 1.565 installed using the RPM package.

-The Linux reference implementation uses CruiseControl 2.8.4-bin installed to _/home/build/tools/cruisecontrol-bin-2.8.4_. 
+You must also configure Jenkins to use the following tools:
+
+#### Java SE JDK
+
+Add a JDK installation for Java SE Development Kit 7u51 to be installed automatically from java.sun.com.
+
+#### Ant
+
+Add an Ant installation for Ant 1.9.2 to be installed automatically from Apache.
+
+#### Maven
+
+Add a Maven installation for Maven 3.1.1 to be installed automatically from Apache.

 ## The Build User

-Create a dedicated, non-administrative user for hosting the build process. In the build user's home directory, create the following subdirectories: 
+Create a dedicated, non-administrative user for hosting the build process. In the build user's home directory, create the following subdirectories:

   * _build-workspace_
   * _scripts_

-The purpose of these directories will be discussed below. 
+The purpose of these directories will be discussed below.

-The Windows reference implementation uses a user named _build_. The user's home directory is logically located at _C:\Documents and Settings\build\My Documents_. 
-
-The Linux reference implementation uses a user named _build_. The user's home directory is logically located at _/home/build_. 
+The Linux reference implementation uses a user named _build_. The user's home directory is logically located at _/home/build_.

 ## Build Scripts

-Several scripts are used to drive the build process. These scripts depend on your specific build environment and thus cannot be provided in a generalized form. The build team provides templates for these scripts in the version control repository. You must download these templates to your build server the first time you set it up. As the Build User, follow these steps to download the templates (~ refers to the build user's home directory): 
+Several scripts are used to drive the build process. These scripts depend on your specific build environment and thus cannot be provided in a generalized form. The build team provides templates for these scripts in the version control repository. You must download these templates to your build server the first time you set it up. As the Build User, follow these steps to download the templates (~ refers to the build user's home directory):

-  1. Change to the directory _~/build-workspace_. 
-  2. Use the Subversion client to download the root build files (note the period at the end of the command representing the current directory): `svn export --force http://gamegineer.svn.sourceforge.net/svnroot/gamegineer/build/trunk .`
-  3. Copy all the script templates in _~/build-workspace/scripts_ to _~/scripts_. Windows servers need only copy the _.bat_ files, while Linux servers need only copy the _.sh_ files. 
-  4. Delete the contents of _~/build-workspace_ to ensure you have a pristine image before bootstrapping the build later. 
+  1. Change to the directory _~/build-workspace_.
+  2. Use the Subversion client to download the root build files (note the period at the end of the command representing the current directory): `svn export --force http://svn.code.sf.net/p/gamegineer/code/build/trunk/ .`
+  3. Copy all the script templates in _~/build-workspace/scripts_ to _~/scripts_. 
+  4. Delete the contents of _~/build-workspace_ to ensure you have a pristine image before bootstrapping the build later.

-Now you must edit each of the script templates you copied. Using a text editor, open each of the script templates and supply appropriate values for the environment variables between the `BEGIN-CUSTOM-VARIABLES` and `END-CUSTOM-VARIABLES` markers. 
+Now you must edit each of the script templates you copied. Using a text editor, open each of the script templates and supply appropriate values for the environment variables between the `BEGIN-CUSTOM-VARIABLES` and `END-CUSTOM-VARIABLES` markers.

-If you are using a VM, you should save this image before continuing. 
+If you are using a VM, you should save this image before continuing.

-The Windows and Linux reference implementations use the directory names defined in the templates. Other variables (e.g. mail host and account information) are not provided in the templates for security purposes. You must have an SMTP account in order to send notifications from your build server. 
+The Linux reference implementation uses the directory names defined in the templates.

 ## Bootstrap the Build Environment

-The first time you set up the build server (or any time you revert to the base build VM image created in the previous step), you must bootstrap the build environment. This is accomplished by running the _~/scripts/bootstrap-build-environment.bat_ script (Windows) or _~/scripts/bootstrap-build-environment.sh_ (Linux). This script simply sets up the _~/build-workspace_ directory with the bootstrap files required by the build environment. 
+The first time you set up the build server (or any time you revert to the base build VM image created in the previous step), you must bootstrap the build environment. This is accomplished by running the _~/scripts/bootstrap-build-environment_ script. This script simply sets up the _~/build-workspace_ directory with the bootstrap files required by the build environment.

 ## Nexus

 ### Create the Nexus Environment

-The Nexus environment must be created every time the Build User logs in to the build server. This is accomplished by running the _~/scripts/nexus-environment.bat_ script (Windows) or sourcing the _~/scripts/nexus-environment.sh_ script (Linux) from a command window. This command window will become the focus of the Gamegineer Nexus environment. This script sets up all environment variables required by Nexus, as well as several other tasks documented in the script. 
+The Nexus environment must be created every time the Build User logs in to the build server. This is accomplished by sourcing the _~/scripts/nexus-environment.sh_ script from a command window. This command window will become the focus of the Gamegineer Nexus environment. This script sets up all environment variables required by Nexus, as well as several other tasks documented in the script.

 ### Start Nexus

-At this point, you are ready to execute Nexus. From the Nexus environment command window you opened in the previous step, run the following command on Windows: 
-    
-    nexus.bat console
-    
+At this point, you are ready to execute Nexus. From the Nexus environment command window you opened in the previous step, run the following command:

-or the following command on Linux: 
-    
     nexus start
-    

 Nexus is now running. 

-Alternatively, on a Linux server, you can execute 
-    
-    ~/scripts/nexus-start.sh
-    
+Alternatively, you can execute:

-to run Nexus as a background process. Note that the _nexus-start.sh_ script performs the steps from the **Create the Nexus Environment** section above, so it is unnecessary to source the _nexus-environment.sh_ script before executing _nexus-start.sh_. Similarly, to stop a running Nexus process, you can execute 
-    
-    ~/scripts/nexus-stop.sh
-    
+    ~/scripts/nexus-start

-## CruiseControl
+to run Nexus as a background process. Note that the _nexus-start_ script performs the steps from the **Create the Nexus Environment** section above, so it is unnecessary to source the _nexus-environment.sh_ script before executing _nexus-start_. Similarly, to stop a running Nexus process, you can execute

-### Create the CruiseControl Environment
+    ~/scripts/nexus-stop

-The CruiseControl environment must be created every time the Build User logs in to the build server. This is accomplished by running the _~/scripts/cc-environment.bat_ script (Windows) or sourcing the _~/scripts/cc-environment.sh_ script (Linux) from a command window. This command window will become the focus of the Gamegineer CruiseControl environment. This script sets up all environment variables required by CruiseControl, as well as several other tasks documented in the script. 
+## Jenkins

-The Windows reference implementation has a shortcut on the Quick Launch toolbar that executes the target: `%comspec% /k "%HOMEDRIVE%%HOMEPATH%\My Documents\scripts\cc-environment.bat"`. 
-
-### Start CruiseControl
-
-At this point, you are ready to execute CruiseControl. From the CruiseControl environment command window you opened in the previous step, run the following command on Windows: 
-    
-    cruisecontrol.bat
-    
-
-or the following command on Linux: 
-    
-    cruisecontrol.sh
-    
-
-CruiseControl will now continuously build the product whenever a change is detected in the version control repository. 
-
-Alternatively, on a Linux server, you can execute 
-    
-    ~/scripts/cc-start.sh
-    
-
-to run CruiseControl as a background process. Note that the _cc-start.sh_ script also performs the steps from the **Create the CruiseControl Environment** section above, so it is unnecessary to source the _cc-environment.sh_ script before executing _cc-start.sh_. Similarly, to stop a running CruiseControl process, you can execute 
-    
-    ~/scripts/cc-stop.sh
-    
+It is recommended to install Jenkins using the RPM package. This will configure Jenkins to automatically start when the server is started.