Table of Contents
This chapter describes how to install the BuildServer software. After installing it, you may choose to run it as a daemon process that interacts with a submit server installation ( see Chapter 7, Running a BuildServer ), or you may choose to run it offline to test individual submissions and test setups ( see Section 5, “To run the BuildServer Offline” ).
Create a fresh directory. I will refer to this directory as
'buildserver' in this chapter but you may name the directory
anything you'd like. Unpack the
BuildServer Module
and
SubmitServerModelClasses Module
into this directory
Change directory into the 'BuildServer' directory.
Make the batch-install and killall scripts executable (chmod u+x). Also make all the scripts in the 'scripts' directory executable.
Run
ant
. The code should compile with no errors. (You may see
warnings about deprecated code; they are normal. The ant build
script expects SubmitServerModelClasses to be next to tbe
BuildServer, and will find and compile it as appropriate).
Run the
batch-install
from inside the BuildServer directory. Here is a sample call
to this script:
./batch-install -h oursubmitserver.ourschool.edu -c
CSE101,"CSE 202" -s "Spring 2006" 4
The courses and semester should correspond to the names you use when you create courses in Chapter 9, Configuring Marmoset. The full usage of this script is:
Usage: ./batch-install
[ -b <buildServerWorkDir> ]
Where to put BuildServer work directories and logfiles; defaults to the current directory (i.e. BuildServer)
[ -f <findbugsDir> ]
If empty then FindBugs won't be used
[ -p <port> ]
Defaults to 8443
[ -u <unprivilegedAccount> ]
Default is to use the same account running the BuildServer (less secure but perfectly functional)
-h <serverHost>
REQUIRED: The hostname of the SubmitServer to connect to
-c <course1,...,courseN>
REQUIRED: Comma-separated list of courses this BuildServer supports
-s <semester>
REQUIRED: The semester for which this BuildServer can build submissions
<numBuildServers>
REQUIRED: The number of BuildServers to create
Table 6.1. Test properties
| Parameter | Required? | Default | Meaning |
|---|---|---|---|
| -b [buildServerWorkDir] | no | The current directory (the batch-install script must be run from the BuildServer directory). | Where to put the work directories for the BuildServers this script creates. The work directories are where the BuildServer stores downloaded submissions and test-setups, and stores its logfiles. These directories will typically be named something like bs2.<hostname> |
| -f [FindBugsDir] | no | don't use FindBugs | If a FindBugs installation is specified, then this BuildServer will run FindBugs on all Java-based submissions, and report the results back to the SubmitServer (which will display them to students and instructors). If no FindBugs installation is specified, then this BuildServer will not use FindBugs. |
| -u [unprivilegedAccount] | no | don't use an unprivileged account | If an unprivileged account is specified, the BuildServer will 'su' to this account before executing student code for Makefile-based projects. (Note that this implies that the account running the BuildServer can 'su' to the unprivileged account with no password.) This provides additional security in that student-written code will not be able to delete anything from the file system. If no unprivileged account is specified, then student-written code will run under the same account that is running the BuildServer. This is somewhat less secure, but perfectly functional. |
| port | no | 8443 | The port on the server where the SubmitServer is running. |
| -h [submitserverHost] | yes | N/A | The hostname of the SubmitServer for BuildServers to connect to. |
| -c <course1,...,courseN> | yes | N/A |
A comma-separated list of the courses that
this BuildServer can compile and test. For
example:
|
| -s [semester] | yes | N/A |
The semester for which this BuildServer can
build and test submissions. For example:
|
| num_build_servers | yes | N/A |
The number of BuildServers to create.
BuildServers will be put into
<buildServerWorkDir>, and will be named:
|