ITK/Policy and Procedure for Adding Dashboards: Difference between revisions

From KitwarePublic
< ITK
Jump to navigationJump to search
No edit summary
Line 26: Line 26:
=== Scheduling a Dashboard Submission ===
=== Scheduling a Dashboard Submission ===
Dashboard submissions can be automatically run with [http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Setting_Up_Cron.2FScheduler Cron or Scheduler].
Dashboard submissions can be automatically run with [http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Setting_Up_Cron.2FScheduler Cron or Scheduler].
=== Advanced Features ===
==== Memory Checker ====
==== Coverage ====
==== Style ====




OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping
OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping

Revision as of 17:03, 28 February 2008

This page is under construction

The nightly and continuous build/test of ITK is essential to its survival. The ITK Dashboard presents dashboard submissions from the ITK community. The dashboards represent unique configurations of hardware platforms, operating systems, compilers, compiler options and ITK options.


Policy

Each dashboard shall present a unique combination of hardware/compiler/OS, optional features and compiler options. The dashboard submitter will monitor the itk dashboard on a routine basis to make sure that the dashboard is reporting as a nightly or continuous build.

Procedure

The recommended method for dashboard submission is using ctest scripts.

Preparing a Dashboard Submission

  1. Use a CMake GUI (CMakeSetup on Windows or ccmake on UNIX) or the wizard mode (cmake -i) to edit cache entries.
  2. Perform a manual build.
  3. Run the tests.
  4. As of ITK 3.6, the configure process creates a file ${ITK_BINARY_DIR}/CMake/itkSampleBuildTest.cmake that contains ctest commands to build, test and submit a configuration that is the same as your configured build.
  5. Copy the itkSampleBuildTest.cmake file to another directory and rename it.
  6. Edit this file to select the type of submission to Nightly or Continuous
  7. Select the build type, either Debug, Release, RelWithDebInfo or MinSizeRel
  8. By default, the script will
    1. For nightly submissions, start with an empty binary directory. If your platform takes an unreasonable time to build from a clean directory, you can change CTEST_START_WITH_EMPTY_DIRECTORY to FALSE.
    2. For continuous submissions, start with an empty binary directory the first time it runs each day. Here again, if your platform takes a long time to build from a clean binary directory, you can change CTEST_START_WITH_EMPTY_DIRECTORY_ONCE to FALSE.
  9. Test your ctest script
    1. ctest -V -S your_script_file

Scheduling a Dashboard Submission

Dashboard submissions can be automatically run with Cron or Scheduler.

Advanced Features

Memory Checker

Coverage

Style

OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping

Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK/Policy_and_Procedure_for_Adding_Dashboards&oldid=11749"