1 | README for NightlyBuild |
---|
2 | |
---|
3 | The NightlyBuild scripts are made for the automatic download, configure, build, and test of COIN-OR projects. |
---|
4 | If a failure is recognized, NightlyBuild can send an e-mail to the corresponding project manager. |
---|
5 | NightlyBuild can also be used to generate automatically binary distributions of COIN-OR projects. |
---|
6 | The main program is nightlyBuild.py |
---|
7 | |
---|
8 | For each supported COIN-OR project a set of build types can be specified. |
---|
9 | A build type is a tuple of information containing the |
---|
10 | - SvnVersion: which version from the repository to built (trunk, latestStable, latestRelease, stable/0.1, ...)? |
---|
11 | - OptLevel: should the code be build in optimized mode ("Default") or debugging mode ("Debug") |
---|
12 | - ThirdParty: should it be allowed to use third party codes |
---|
13 | - SkipProjects: a list of COIN-OR projects (from the externals) that should be skipped in the build |
---|
14 | - AdditionalConfigOptions: additional flags for the configure call |
---|
15 | |
---|
16 | For such a build type, NightlyBuild does |
---|
17 | 1. Checkout the specified version from the svn repository (https://projects.coin-or.org/svn/<project>/...). |
---|
18 | 2. Download third party codes for which get.XXX scripts can be found. |
---|
19 | 3. Assemble the parameter for the configure call. |
---|
20 | 4. Call configure. If there is an error, send a failure report as e-mail and break. |
---|
21 | 5. Call make. If there is an error, send a failure report as e-mail and break. |
---|
22 | 6. If the project has a test program, call make test. If there is an error, send a failure report as e-mail and break. |
---|
23 | 7. If the project has unit tests, call the unit tests. If there is an error, send a failure report as e-mail and break. |
---|
24 | |
---|
25 | There are also rules implemented to avoid the rebuild and test of a project if there has been no change in the code since the last build. |
---|
26 | The failure reports contain, next to information about the build type and the system, also the output to stdout and stderr. |
---|
27 | The output of get.XXX scripts, configure, make, unittests to stdout and stderr is also stored in the build directories for later analysis (e.g., NBmake.stdout). |
---|
28 | |
---|
29 | To install and use NightlyBuild please see the INSTALL file. |
---|