Difference between revisions of "Autobuild Config"
(→Steps) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {| align="right" | ||
| + | | __TOC__ | ||
| + | |} | ||
So you want to set up an autobuild site? This is how our current nightly autobuild is configured. | So you want to set up an autobuild site? This is how our current nightly autobuild is configured. | ||
| Line 5: | Line 8: | ||
* Maven | * Maven | ||
* Ant | * Ant | ||
| + | * Java SDK | ||
| + | * SVN | ||
* Continuum | * Continuum | ||
| − | * | + | * Putty |
== Assumptions == | == Assumptions == | ||
| − | It is assumed that you have a working build environment as detailed in [[Building_PCGen]] | + | * It is assumed that you have a working build environment as detailed in [[Building_PCGen]] and can run SVN from the command line. |
| + | * Putty should be in your path | ||
== Steps == | == Steps == | ||
| Line 23: | Line 29: | ||
# Create a new schedule for the nightly build | # Create a new schedule for the nightly build | ||
# Add a new build definition. The goal should be '''clean:clean jar pcgen:package site:deploy''' and uses the nightly schedule | # Add a new build definition. The goal should be '''clean:clean jar pcgen:package site:deploy''' and uses the nightly schedule | ||
| + | # Create a build.properties file as listed below | ||
# Once the download has completed, manually start the build to test it | # Once the download has completed, manually start the build to test it | ||
| + | |||
| + | == Build Properties File == | ||
| + | |||
| + | You will need a build.properties file in your home directory (usually C:\Documents and Settings\username in Windows) with the following contents: | ||
| + | <pre> | ||
| + | maven.username=sfuserid | ||
| + | maven.password=sfpassword | ||
| + | maven.scp.executable=pscp | ||
| + | maven.ssh.executable=plink | ||
| + | </pre> | ||
| + | |||
| + | |||
| + | == Troubleshooting == | ||
| + | * SourceForge's SVN seems to drop out regularly. As a result you may need to coax the initial download from SVN along manually. You can do this by opening a shell or command window in the project working directory and running '''svn update''' | ||
| + | * If things seem to have paused or are not working, check the wrapper.log in the logs folder. | ||
| + | * If you get an error saying the working directory is locked, open a shell or command window in the project working directory and run '''svn cleanup''' | ||
Latest revision as of 11:59, 17 September 2008
So you want to set up an autobuild site? This is how our current nightly autobuild is configured.
Requirements
- Maven
- Ant
- Java SDK
- SVN
- Continuum
- Putty
Assumptions
- It is assumed that you have a working build environment as detailed in Building_PCGen and can run SVN from the command line.
- Putty should be in your path
Steps
- Download and install Continuum 1.1
- Configure the email settings as noted in the install docs
- Start Continuum and go to the default page - http://localhost:8080/continuum
- Create an admin user and then login
- Set the config options as appropriate
- Add Project - Maven 1.x
- Upload the project.xml from the pcgen directory and click Add
- Continuum will download the project
- Create a new schedule for the nightly build
- Add a new build definition. The goal should be clean:clean jar pcgen:package site:deploy and uses the nightly schedule
- Create a build.properties file as listed below
- Once the download has completed, manually start the build to test it
Build Properties File
You will need a build.properties file in your home directory (usually C:\Documents and Settings\username in Windows) with the following contents:
maven.username=sfuserid maven.password=sfpassword maven.scp.executable=pscp maven.ssh.executable=plink
Troubleshooting
- SourceForge's SVN seems to drop out regularly. As a result you may need to coax the initial download from SVN along manually. You can do this by opening a shell or command window in the project working directory and running svn update
- If things seem to have paused or are not working, check the wrapper.log in the logs folder.
- If you get an error saying the working directory is locked, open a shell or command window in the project working directory and run svn cleanup
