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

Revision as of 14:08, 23 June 2014

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

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

Determine how maintenance of the factory machines will be handled
- Do we have enough machines?
- How can the community help? (setting up and maintaing dashboard machines)
Are there other technologies or systems we should leverage, e.g. travis-ci
- I've had good luck setting up a dashboard machine with for CTK
  - this travis config script
  - triggers a build like this
  - that 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
  - 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
  - Mac and Windows build machines are in beta
- There is a commercial version of travis for priority access and private repositories
Address questions discussed in this slicer-devel email thread
- Gerrit vs github
- Review Board
Other ideas we should consider?

@@ Line 25: / Line 25: @@
 *** 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].
-** Have not yet tries Slicer on travis
+** Have not yet tried Slicer on travis
 *** potential issue: 90 minute limit
 *** may be addressed by a build-matrix (i.e. subgroups of tests)