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:
- svn update (if no changes occured, the script ends)
- do a clean build (release and debug version)
- run unittests (currently linux only)
- build and upload packages
- build and upload documentation (linux only)
- run the acceptance tests (texttest)
- upload test results
All the results can be found in the daily dir on the sumo web space, also see Downloads#Nightly_Snapshots. There is also a local copy in the Daten/Sumo/daily directory (including the most recent game scenarios) the DLR internal tsall NAS. The windows script uses the sumo-all package from the local dir to build the binary distributable zip and the game zip.
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.