Difference between revisions of "2014 Summer Project Week: Factory and Testing Process Post NA-MIC"
From NAMIC Wiki
| 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 31: | Line 31: | ||
*** 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 | + | *** [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] | ||
Revision as of 14:15, 23 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
- I've had good luck setting up a dashboard machine with for CTK
- 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 on the horizon, but not clear when
- 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?
Approach, Plan
- Have a breakout discussion and document results here
