Top .NET dog Roy Osherove just blogged some good questions about choosing a build automation or CI tool. This comes hot on the heels of his post about the difference between continuous build and continuous integration.
Here’s a few more questions:
- If someone breaks the config, can I roll it back?
- If not, can I secure it so that people can manage their own projects?
- Can I use the tool to help release code as well as build/test/integrate?
- Is there an ecosystem around the tool? (plugins, etc)
- Can I trace artifacts of a build back to the original commit?
- Is it platform agnostic (I won’t go back to the days of 3 ports of CruiseControl, thanks very much)
What would your questions be?
Related posts:
- Every Continuous Integration server that supports Ruby + Git As I posted, I’m on a quest for the...
- Continuous Integration is an attitude Question: How do we prevent integration pain? Answer: Continuous Integration....
- The quest for a decent Ruby Continuous Integration tool Git has become very popular in the Ruby community. Github...
- 6 Big Visible Continuous Integration Tools I love Information Radiators. You can have all the Twitter...
- New Continuous Integration system I got a mail a few weeks ago from Mr...
Related posts brought to you by Yet Another Related Posts Plugin.