Simpson says, "CruiseControl was a fantastic brand for ThoughtWorks. You can understand why they decided to base the name for their new, commercially licensed Continuous Integration server on the old." The problem was that praise and/or criticism was being misdirected towards TWS's commercial CI server, Cruise. Cruise Control, by contrast, is a CI tool and framework that is open source. The two technologies are different, but they both deal with Continuous Integration, so the similar uses and similar names easily confused people.
Here's a quote that Simpson posted from his conversation with Chad Wathington, the VP of product development at TWS:
We built Cruise with the idea of first class support for build and deployment pipelines. We’ve renamed Cruise to Go because we really want to take that idea to the next level, to emphasize continuous deployment, to emphasize “going live” with software, not just continuous integration. Beyond the name change, we’ve added support for environment management and we’ve revamped the user experience to fit our deployment pipeline metaphor more strongly. We think people are going to like it.
The official renaming of 'Cruise' to 'Go' hasn't happened yet, as you can see on the TWS website, where it's still called Cruise. There's still some criticism against the new name, which is the same as Google's new 'Go' programming language. However, given that one is a language, and the other is a commercial CI product, I'm sure we'll know which "Go" someone is talking about by seeing the context.
The most recent version of Cruise (2.0) has a number of features that makes it very easy to manage builds and testing infrastructure for large organizations. Features include:
- Reusable workflow templates
- CI builds with any revision from version control
- Build-grid partitioning, which can run test suites with automatic analysis
- The ability to deploy any version of any application to any environment and manage multiple services that share the same environment