Difference between revisions of "2011 Winter Project Week:Dashboards Factory machine subprojects and CDashAtHome"

From NAMIC Wiki
Jump to: navigation, search
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2011.png|Projects List </gallery> ==Key Investigators== * Kitware: David Partyka, Zack Galbreth, JC, Zach M…')
 
Line 13: Line 13:
 
<h3>Objective</h3>
 
<h3>Objective</h3>
 
Introduce the Slicer community to several new software process tools.
 
Introduce the Slicer community to several new software process tools.
* CDash@Home and it's availability on Factory. Also Demonstrate
+
* CDash@Home and it's availability on Factory.
* SubProjects
+
* New SubProjects Dasbhoard.
  
 
</div>
 
</div>
Line 21: Line 21:
  
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
There are several fronts that needs to be investigated.
+
*CDash@Home is a new technology now available to Slicer developers allowing them to trigger builds of Slicer on each of Mac, Windows and Linux remotely before checking their code into the main repository. This should help the Slicer community improve the quality of the code checked into Slicer as well as allow developers to offload testing their code onto the Factory machines on demand.
* Updating all prebuilt tcl libraries to also include 64bit versions.
+
*SubProjects is a new CDash feature that allows us to granualize the components of Slicer at the Dashboard level allowing one to see exactly how a particular commit affects the different components of Slicer, from build errors and warnings down to coverage and valgrind results. Utilizing Subprojects Slicer should be able to easily detect deficiencies and also improve accountability.  
* Discuss what to do about ITK3. It can be compiled 64bit but infact doesn't actually support loading data >4GB.
 
 
</div>
 
</div>
  
Line 29: Line 28:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
Several discussions have occurred particularly regarding the fact that ITK4 now has support for loading large data. Further discussion is needed to see how Slicer may want to move forward with moving to ITK4.
+
*CDash at home is currently up and running on the Factory, Factory-win7 and Factory-ubuntu machines.
 +
*Subproejct development is currently being tested on http://my.cdash.org/index.php?project=Slicer4-Modules&date= dashboard.
  
 
</div>
 
</div>

Revision as of 19:38, 8 January 2011

Home < 2011 Winter Project Week:Dashboards Factory machine subprojects and CDashAtHome

Key Investigators

  • Kitware: David Partyka, Zack Galbreth, JC, Zach Mullen, Stephen Aylward
  • SPL: Steve Pieper

Objective

Introduce the Slicer community to several new software process tools.

  • CDash@Home and it's availability on Factory.
  • New SubProjects Dasbhoard.

Approach, Plan

  • CDash@Home is a new technology now available to Slicer developers allowing them to trigger builds of Slicer on each of Mac, Windows and Linux remotely before checking their code into the main repository. This should help the Slicer community improve the quality of the code checked into Slicer as well as allow developers to offload testing their code onto the Factory machines on demand.
  • SubProjects is a new CDash feature that allows us to granualize the components of Slicer at the Dashboard level allowing one to see exactly how a particular commit affects the different components of Slicer, from build errors and warnings down to coverage and valgrind results. Utilizing Subprojects Slicer should be able to easily detect deficiencies and also improve accountability.

Progress

Delivery Mechanism

This work will be incorporated into Slicer.