FinalBuilder vs GoCD
When comparing FinalBuilder vs GoCD, the Slant community recommends GoCD for most people. In the question“What are the best continuous integration tools?” GoCD is ranked 18th while FinalBuilder is ranked 32nd. The most important reason people chose GoCD is:
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Well documented
One of the few websites with useful information about Code Signing with USB Tokens.
Pro Pre-written scripts available
FinalBuilder has more than 600 pre-written scripts (known as actions) available. These actions help automate common tasks in a build process. This saves a lot of development time because you don't have to write those common tasks yourself.
Pro Native support for pipelines
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Pro Good traceability of what contributed to a given artifact
GoCD's LEAN value stream UI helps all stakeholders focus on efficient product delivery (instead of collections of technical tasks).
Cons
Con Not free nor open source
Con Diff on finalbuilder projects are clumsy
Con "Click button" interface
Con Builds are a little unintuitive
The language used in the documentation is a little ambiguous and FinalBuilder feels a little clunky when setting up builds.
Con Need Scripts for everything
Almost all operations are shell based, they are not configurations possible, your CI is as good as your scripting
Con Does not offer many plugins
Since it's relatively new and not very popular, there are few plugins available in GoCD.