2,561
edits
FlightGear build server: Difference between revisions
Jump to navigation
Jump to search
m
→Options: DOXYGEN: copying from http://wiki.flightgear.org/index.php/Project_Infrastructure_Enhancements#Build.2FRelease_related
m (→Options: linking to FlightGear Headless) |
m (→Options: DOXYGEN: copying from http://wiki.flightgear.org/index.php/Project_Infrastructure_Enhancements#Build.2FRelease_related) |
||
| Line 113: | Line 113: | ||
* So, another step is to email committers directly when they break the build. If you're a commiter to FG or SG, you may see some odd emails | * So, another step is to email committers directly when they break the build. If you're a commiter to FG or SG, you may see some odd emails | ||
* set up [http://www.doxygen.org/ doxygen] to automatically create source code documentation for simgear and flightgear using the build server checkouts | |||
* set up a buildser...@flightgear.org address. | * set up a buildser...@flightgear.org address. | ||
* Yet another thing it can do is run test suites - unfortunately we don't have many such tests at the moment. (also see [[FlightGear Headless]]) | * Yet another thing it can do is run test suites - unfortunately we don't have many such tests at the moment. (also see [[FlightGear Headless]]) | ||
* determine if/how tools like valgrind and gprof could be used to automatically create regression statistics for each build | |||
* using ccache or even distcc might help speed up build times | |||
* If anyone wants to get into providing nightly .debs or .rpms, that could also be done, but requires people who know those systems, and again can provide a suitable externally address slave to run the builds. | * If anyone wants to get into providing nightly .debs or .rpms, that could also be done, but requires people who know those systems, and again can provide a suitable externally address slave to run the builds. | ||