CodeRush vs. GoCD

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CodeRush
Score 7.0 out of 10
N/A
CodeRush is a tool for Visual Studio that offers refactoring for C#, Visual Basic, and XAML, with a .NET test runner and debugging. It is available as a free download.N/A
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.N/A
Pricing
CodeRushGoCD
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CodeRushGoCD
Free Trial
NoNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CodeRushGoCD
Considered Both Products
CodeRush

No answer on this topic

GoCD
Chose GoCD
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to …
Chose GoCD
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The …
Best Alternatives
CodeRushGoCD
Small Businesses
GitHub
GitHub
Score 9.0 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
Veracode
Veracode
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.6 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CodeRushGoCD
Likelihood to Recommend
-
(0 ratings)
9.0
(0 ratings)
User Testimonials
CodeRushGoCD
Likelihood to Recommend
No answers on this topic
GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.
Read full review
Pros
No answers on this topic
  • Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
  • The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
  • Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
Read full review
Cons
No answers on this topic
  • UI can be improved
  • Location for settings can be re-arranged
  • API for setting up pipeline
Read full review
Alternatives Considered
No answers on this topic
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.
Read full review
Return on Investment
No answers on this topic
  • ROI has been good since it's open source
  • Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
  • More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
Read full review
ScreenShots