Daily Build Procedure

Schedule: Daily Builds Will Occur Sun, Tue, Thu, Fri (6pm)

Downloads

autoBuild 2KB Automated Build File


Automated Build Procedure

Note: Subversion and a Secure Shell Client must be installed.
The machine/server you are building on must have JDK 1.6 or above installed to successfully build ChangeStyle-Stage_2.0.

Run the Build

1. Log onto a linux machine or SSH to a Cal Poly server such as vogon.
2. Download the Automated Build above. Save the the file to a directory of your choosing.
3. Open a New Terminal Window and navigate to the directory you chose.
4. Type "autoBuild" and wait for the build to complete. Note: This may take a few minutes.

Verify the Build

1. Open a browser to http://wiki.csc.calpoly.edu/Luna/browser/dailybuilds and verify that a new build folder with the current date exists.
2. Click on the build folder -> output.txt. Look for compile errors in the output.txt file. If an error occurred follow the Broken Build Procedure below.

Update Daily Build Reports

1. Go to the DailyBuilds page.
2. Log in. (You will need to be part of team Luna to have access)
3. Click Edit.
4. Add a new line to the page including the Date Built, Status, and Build ID(date).
5. Also add links to the build folder files you created; an SVNLog link, BuildOutput? link, and changestyle.jar link.
6. Done.

Manual Build Procedure

Note: Eclipse (Ver 3.3 or newer) and an SVN tool, either TortoiseSVN (Tor) or Subversion (Sub) must be installed.
The machine/server you are building on must have JDK 1.6 or above installed to successfully build ChangeStyle-Stage_2.0.

Get the Current SVN Repository

1. Move to the Directory you want to Checkout the Repository. I called my Directory "SVN".
2. Checkout the Repository

  1. (Sub) Type "svn co http://wiki.csc.calpoly.edu/Luna/svn/ ./SVN"
  2. (Tor) Right-Click->SVN Checkout


Set Up the WorkSpace?

1. Open an Eclipse Workspace. I called my Workspace "DailyBuild?".
2. Import the current ChangeStyle Branch, I will use "ChangeStyle-1.0" as an example, into Eclipse and the current Jalopy resource.

  1. Click File->Import->Existing Projects into Workspace->"SVN/trunk/branches/archive/Stage-1.0/ChangeStyle-1.0".
  2. Click File->Import->Existing Projects into Workspace->"SVN/trunk/branches/archive/Stage-1.0/jalopy-1.5rc3.1".

3. Ensure Project->Build Automatically is checked.
4. If Errors Occur, Refresh the projects by

  1. Clicking on the Project Folders in the left tab and pressing F5
  2. OR Right-Click Project Folders in the left tab and selecting "Refresh".

5. If Errors still exist, follow the Broken Build Procedure.

Build the Jar

1. Right-Click the jardesc in the ChangeStyle-1.0 folder and select "Create JAR". The jar will be created in the parent directory of the workspace and will be named "changestyle.jar".
2. Keep Eclipse open

Update Daily Build Area

1. Move to the "SVN/dailybuilds" directory.
2. Create a folder that follows the format "build_mm.dd.yy", where the number is the current date.
3. Move to the newly created build folder.
4. Copy the created "changestyle.jar" into the build folder.
4. Create an "output.txt" file and a "log.txt" file.
5. In Eclipse, click the Problems Tab on the bottom and Right-Click "Warnings" -> Select All
6. Copy and paste the results into the output.txt file.
7. Copy the SVN log file

  1. (Sub) Type "svn log > log.txt".
  2. (Tor) Right-Click the "SVN" folder -> TortoiseSVN -> Show Log. Click "Show All". Select all the Log Messages. Copy and paste the results into the log.txt file.

Update Daily Build Reports

1. Go to the DailyBuilds page.
2. Log in. (You will need to be part of team Luna to have access)
3. Click Edit.
4. Add a new line to the page including the Date Built, Status, and Build ID(date).
5. Also add links to the build folder files you created; an SVNLog link, BuildOutput? link, and changestyle.jar link.
6. Done.

Broken Build Procedure

For each error in the build output, identify the module that has the error, go to the Integration Plan and find the owner of that module. From the team contact list, obtain their telephone number. Phone them and inform them that their module broke the build and they should consult the build report for details. If you can't reach them in person leave a message and also send an e-mail. Assuming the build was run at 6pm as scheduled, ask them to call you back by 10pm with the status. Append the letter 'A' to the Build ID in the Build Report. Put any relevant remarks in place of the Download link.

IF the developer calls by 10pm THEN

IF the status is fixed THEN rerun the daily build procedure.
ELSE change letter ‘A’ to ‘B’, email team manager and inform her that the build is broken, and revert the build to last successful version and update build report.

IF the developer doesn't call by 10pm THEN

Change letter ‘A’ to ‘B’, email team manager and inform her that the build is broken and you've been unable to contact developer, and revert the build to last successful version and update build report.