Developer/Nightly Build

There are two main scripts responsible for the nightly build process which are tools/build/dailyUpdateMakeGCC (for the linux part) and tools/build/dailyBuildMSVC.py for windows. Essentially they both perform the following steps: All the results can be found in the daily dir on the sumo web space, also see Downloads. The binaries and the packages (but no test results) are also in the Daten/Sumo/Nightly directory on the DLR internal vm_tausch. The windows script uses the source and the doc package from the vm_tausch to build the binary distributable zip.
 * 1) svn update (if no changes occured, the script ends)
 * 2) do a clean build (release and debug version)
 * 3) run unittests (currently linux only)
 * 4) build and upload packages
 * 5) build and upload documentation (linux only)
 * 6) run the acceptance tests (texttest)
 * 7) upload test results

One final step is to trigger the nightly build on the opensuse build service. This is achieved via uploading a new spec file via a cronjob, which triggers an automatic download of the sources and a rebuild. All errors and test result e-mails are directed to the sumo-tests list at dlr.de, except for the build service errors which go to a private account since the build is currently in a private project.