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:
- Continuous Integration is an attitude Question: How do we prevent integration pain? Answer: Continuous...
- Presentation: Continuous Integration from the trenches I presented this talk at QCon London in March...
- Justifying Continuous Integration Expenditure Banos commented on my last post: So why, oh...
- Continuous Integration Quick Reference Continuous Integration is frequently written about. That’s all good....
- Continuous Integration in the cloud: good idea? Continuous Integration can be tricky to provision. It’s IO...
Related posts brought to you by Yet Another Related Posts Plugin.
