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

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

Key Investigators

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? (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
  - 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 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?

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
- 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.