ITK/Policy and Procedure for Adding Dashboards: Difference between revisions
From KitwarePublic
< ITK
Jump to navigationJump to search
(New page: '''This page is under construction''' The nightly and continuous build/test of ITK is essential to its survival. The [http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashbo...) |
No edit summary |
||
| Line 2: | Line 2: | ||
The nightly and continuous build/test of ITK is essential to its survival. The [http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html 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. | The nightly and continuous build/test of ITK is essential to its survival. The [http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html 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 === | |||
# Using a cmake GUI (cmakesetup or ccmake), configure the build with the desired options. | |||
# Perform a manual build | |||
# Run the tests | |||
# As of ITK 3.4, 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. | |||
# Copy the ''itkSampleBuildTest.cmake'' file to another directory and rename it. | |||
# Edit this file to select the type of submission to Nightly or Continuous | |||
# Select the build type | |||
=== Scheduling a Dashboard Submission === | |||
OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping | OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping | ||
Revision as of 13:59, 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
- Using a cmake GUI (cmakesetup or ccmake), configure the build with the desired options.
- Perform a manual build
- Run the tests
- As of ITK 3.4, 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.
- Copy the itkSampleBuildTest.cmake file to another directory and rename it.
- Edit this file to select the type of submission to Nightly or Continuous
- Select the build type
Scheduling a Dashboard Submission
OS Compiler Debug/Release Static/Shared 32/64 bit Wrapping
