Difference between revisions of "2014 Summer Project Week: Factory and Testing Process Post NA-MIC"

From NAMIC Wiki
Jump to: navigation, search
 
(3 intermediate revisions by the same user not shown)
Line 18: Line 18:
 
<h3>Objective</h3>
 
<h3>Objective</h3>
 
* Determine how maintenance of the factory machines will be handled
 
* Determine how maintenance of the factory machines will be handled
** Do we have enough machines?
+
** Do we have enough machines? (mac, windows, linux cloud servers needed?)
 
** How can the community help? (setting up and maintaing dashboard machines)
 
** How can the community help? (setting up and maintaing dashboard machines)
 
* Are there other technologies or systems we should leverage, e.g. [http://travis-ci.org travis-ci]
 
* Are there other technologies or systems we should leverage, e.g. [http://travis-ci.org travis-ci]
Line 25: Line 25:
 
*** triggers [https://travis-ci.org/pieper/CTK/builds/28169843 a build like this]  
 
*** triggers [https://travis-ci.org/pieper/CTK/builds/28169843 a build like this]  
 
*** that [http://my.cdash.org/index.php?project=CTK&date=2014-06-22#Experimental submits to the dashboard on every commit].
 
*** that [http://my.cdash.org/index.php?project=CTK&date=2014-06-22#Experimental submits to the dashboard on every commit].
 +
** Have not yet tried Slicer on travis
 +
*** potential issue: 90 minute limit
 +
*** may be addressed by a build-matrix (i.e. subgroups of tests)
 
** Travis is free for open projects
 
** Travis is free for open projects
 
*** Builds are triggered by git pushes to github (to any branch or pull request)
 
*** Builds are triggered by git pushes to github (to any branch or pull request)
 
*** Build machine is ubuntu 12.04, X server with GLX can be supported
 
*** Build machine is ubuntu 12.04, X server with GLX can be supported
*** Mac and Windows build machines are in beta
+
*** [https://github.com/travis-ci/travis-ci/issues/216 Mac and Windows build machines] are on the horizon, but not clear when
 
** There is a [http://travis-ci.com commercial version of travis] for priority access and private repositories
 
** There is a [http://travis-ci.com commercial version of travis] for priority access and private repositories
 
* Address questions discussed in [http://massmail.spl.harvard.edu/public-archives/slicer-devel/2014/thread.html#15648 this slicer-devel email thread]
 
* Address questions discussed in [http://massmail.spl.harvard.edu/public-archives/slicer-devel/2014/thread.html#15648 this slicer-devel email thread]
Line 41: Line 44:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
*
+
* Reviewed travis-ci status
 +
** system looks like it works well for CTK on linux
 +
** questions of squeezing slicer build into 90 minute windows, but could be done with refactoring
 +
* Discussed possible alternative build systems
 +
** [http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-continuous-delivery/ Microsoft Azure for windows?]
 +
** Other continuous integration and content delivery systems are more web-oriented
 +
* Some additional dedicated machines could be useful if we can afford to buy them, but would prefer cloud machines.
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 21:13, 26 June 2014

Home < 2014 Summer Project Week: Factory and Testing Process Post NA-MIC

Key Investigators

  • Steve Pieper, Isomics
  • Jc, Kitware
  • Ron, BWH/Mevis
  • (others?)

Project Description

Discuss maintenance issues and priorities for Slicer and Extension nightly builds as NA-MIC itself winds down.

Objective

  • Determine how maintenance of the factory machines will be handled
    • Do we have enough machines? (mac, windows, linux cloud servers needed?)
    • How can the community help? (setting up and maintaing dashboard machines)
  • Are there other technologies or systems we should leverage, e.g. travis-ci
  • Address questions discussed in this slicer-devel email thread
  • Other ideas we should consider?

Approach, Plan

  • Have a breakout discussion and document results here

Progress

  • Reviewed travis-ci status
    • system looks like it works well for CTK on linux
    • questions of squeezing slicer build into 90 minute windows, but could be done with refactoring
  • Discussed possible alternative build systems
  • Some additional dedicated machines could be useful if we can afford to buy them, but would prefer cloud machines.