Difference between revisions of "Documentation/4.0/Developers/Tutorials/DashboardSetup"
m |
m |
||
Line 66: | Line 66: | ||
The output of the build is contained in SlicerFunctionCTestPackage-make-package-output.txt" in your slicer build directory, you can check this file if something went wrong. | The output of the build is contained in SlicerFunctionCTestPackage-make-package-output.txt" in your slicer build directory, you can check this file if something went wrong. | ||
+ | |||
+ | = Remarks = |
Revision as of 13:03, 14 November 2011
Home < Documentation < 4.0 < Developers < Tutorials < DashboardSetupPrerequisites
Use CMake version >= 2.8.5
Setup
Follow the following instructions to set up dashboard: (by JC, from [1])
$ cd ~ $ mkdir Dashboards $ mkdir DashboardScripts $ cd DashboardScripts $ wget http://svn.slicer.org/Slicer4/trunk/CMake/SlicerDashboardScript.TEMPLATE.cmake $ mv SlicerDashboardScript.TEMPLATE.cmake <MachineName>_<OperatingSystem>-64bits_slicer_release_nightly.cmake
Edit the file <MachineName>_opensuse_slicer_release_nightly.cmake to match your machine settings. You should update the following variables:
set(MY_OPERATING_SYSTEM "<OperatingSystem>") # Windows, Linux, Darwin... set(MY_COMPILER "g++4.4.3") set(MY_QT_VERSION "4.7") set(QT_QMAKE_EXECUTABLE "$ENV{HOME}/Projects/qtsdk-2010.05/qt/bin/qmake") set(CTEST_SITE "karakoram.kitware") set(CTEST_DASHBOARD_ROOT "$ENV{HOME}/Dashboards/") set(CTEST_CMAKE_COMMAND "/home/jchris/Projects/cmake-2.8.4/bin/cmake") ... set(CTEST_BUILD_CONFIGURATION "Release") ... set(SCRIPT_MODE "nightly")
If git and svn are not in the path, make sure to set the variables CTEST_SVN_COMMAND and CTEST_GIT_COMMAND.
So that your dashboard can automatically start at 11pm daily, you could add an entry similar to the following one in your crontab. (On ubuntu, I am running crontab -e to edit the current user cron list)
0 11 * * * /path/to/cmake-2.8.5/bin/ctest -S /Users/JOE/DashboardScripts/<MachineName>_<OperatingSystem>-64bits_slicer_release_nightly.cmake -VV -O /Users/JOE/Dashboards/Logs/<MachineName>-<OperatingSystem>-64bits_slicer_release_nightly.log
You can use CTEST_BUILD_FLAGS to set the number of CPUs to be used by make (eg, -j4), and CTEST_PARALLEL_LEVEL to set the number of tests to run in parallel (see comments in the configuration script).
Setting up a continuous dashboard
Similarly if you want to setup a continuous dashboard,
$ cp <MachineName>_<OperatingSystem>-64bits_slicer_release_nightly.cmake <MachineName>_opensuse-64bits_slicer_release_continuous.cmake
Edit <MachineName>_<OperatingSystem>-64bits_slicer_release_continuous.cmake and set
set(SCRIPT_MODE "*continuous*")
Then add the corresponding entry in crontab so that it starts everyday at 6am:
0 6 * * * /path/to/cmake-2.8.5/bin/ctest -S /Users/JOE/DashboardScripts/<MachineName>_<OperatingSystem>-64bits_slicer_release_continuous.cmake -VV -O /Users/JOE/Dashboards/Logs/<MachineName>_<OperatingSystem>-64bits_slicer_release_nightly.log
The output of the build is contained in SlicerFunctionCTestPackage-make-package-output.txt" in your slicer build directory, you can check this file if something went wrong.