Difference between revisions of "2014 Summer Project Week: Factory and Testing Process Post NA-MIC"
From NAMIC Wiki
Line 32: | Line 32: | ||
* 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] | ||
** Gerrit vs github | ** Gerrit vs github | ||
+ | ** [http://www.reviewboard.org/ Review Board] | ||
* Other ideas we should consider? | * Other ideas we should consider? | ||
</div> | </div> |
Revision as of 14:04, 23 June 2014
Home < 2014 Summer Project Week: Factory and Testing Process Post NA-MICKey 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?
- 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
- 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?
Approach, Plan
- Have a breakout discussion and document results here