Optional: If you already have bjam and/or process_jam_log executables you'd like to use, just put them in the same directory with regression.py, e.g.:
my_boost_regressions/ regression.py bjam.exe
To start a regression run, simply run regression.py providing it with the only required option, runner id (something unique of your choice that will identify your results in the reports 1). For example:
python regression.py --runner=Metacomm
You can specify a particular set of toolsets you want to test with by passing them as a comma-separated list using the --toolsets option:
python regression.py --runner=Metacomm --toolsets=gcc,vc7
If you are interested in seeing all available options, run python regression.py or python regression.py --help.
Note: If you are behind a firewall/proxy server, everything should still "just work". In the rare cases when it doesn't, you can explicitly specify the proxy server parameters through the --proxy option, e.g.:
python regression.py --runner=Metacomm --proxy=http://www.someproxy.com:3128
| [1] | If you are running regressions interlacingly with a different set of compilers (e.g. for Intel in the morning and GCC at the end of the day), you need to provide a different runner id for each of these runs, e.g. your_name-intel, and your_name-gcc. |
The regression run procedure will:
The report merger process running on MetaCommunications site every 2 hours will merge all submitted test runs and publish them at http://boost.sourceforge.net/regression-logs/developer.