source: branches/testScripts/README @ 740

Last change on this file since 740 was 739, checked in by jpfasano, 12 years ago

Initial effort for building on windows with MS solution file.

  • Property svn:eol-style set to native
File size: 2.0 KB
Line 
1README for NightlyBuild
2
3The NightlyBuild scripts are made for the automatic download, configure, build, and test of COIN-OR projects.
4If a failure is recognized, NightlyBuild can send an e-mail to the corresponding project manager.
5NightlyBuild can also be used to generate automatically binary distributions of COIN-OR projects.
6The main program is nightlyBuild.py
7
8For each supported COIN-OR project a set of build types can be specified.
9A 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
16For such a build type, NightlyBuild does
171. Checkout the specified version from the svn repository (https://projects.coin-or.org/svn/<project>/...).
182. Download third party codes for which get.XXX scripts can be found.
193. Assemble the parameter for the configure call.
204. Call configure. If there is an error, send a failure report as e-mail and break.
215. Call make. If there is an error, send a failure report as e-mail and break.
226. If the project has a test program, call make test. If there is an error, send a failure report as e-mail and break.
237. 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
25There 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.
26The failure reports contain, next to information about the build type and the system, also the output to stdout and stderr.
27The 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
29To install and use NightlyBuild please see the INSTALL file.
Note: See TracBrowser for help on using the repository browser.