QuartzWare - Team


	"Timeless Software Solutions"

Build Procedure .

1. Merge Code Changes: The developer updates his private copy with the master files, to ensure that all files are uptodate, using CVS.

2. Build and test private relase: The developer builds his uptodate code to be sure that there are no conflicts with the master files. He then runs a private smoke test to ensure that the new function works with the master files.

3. Execute the smoke test: The developer runs the current smoke test on his private build, to check that there are no conflicts with existing functionality.

4. Check in: The developer commits his updated code to the master build using CVS.

5. Generate the daily build:

1. The Integration Manager checks out all files from CVS using his personal account.

2. They are then FTP'ed up to his computer.

3. He then compiles them, by running compjar.bat.

4. He records any errors during the compile on the build report and notifies the coder that introduced the error to fix the problem immediately.

6. Run the smoke test:

1. The Integration Manager runs the new build, by using runRBEdit.bat. He will run through the smoke test cases, as well as a simple test of each new function on the new build.

2. Any errors that are found are reported on the Smoke Test Report and posted on Teamatic

7. Update web site:

1. The Integration Manger updates the javadocs, by running compdocs.bat, and posts them on the team web site.

2. He will then zip the jar file and runRBEdit.bat and post them on the team web site.

Builds will be run Monday at 10:30, Wednesday, and Sunday at 8:30 pm if new functionality has been completed.

1-24-01 Document Created Cliff Rowley

2-5-01 Document edited Cliff Rowley

2-11-01 Document edited again, by Cliff.

2-21-01 Changed days of Builds, Tony Johansen

2-23-01 Updated the build steps, Tony Johansen