TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    GoCD

    Score8 out of 10
    N/AGoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.N/A

    Spinnaker

    Score7.9 out of 10
    N/ASpinnaker is an open source continuous delivery platform with a range of cluster management and deployment management features, originally developed at Netflix.N/A
    Pricing
    GoCDSpinnaker
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    GoCDSpinnaker
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Best Alternatives
    GoCDSpinnaker
    Small Businesses
    Apache Maven
    Score9 out of 10
    Octopus Deploy
    Score8.8 out of 10
    Medium-sized Companies
    Apache Maven
    Score9 out of 10
    Octopus Deploy
    Score8.8 out of 10
    Enterprises
    Gradle Build Tool (Open Source)
    Score9 out of 10
    Octopus Deploy
    Score8.8 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    GoCDSpinnaker
    Likelihood to Recommend
    9.0
    (2 ratings)
    7.0
    (3 ratings)
    User Testimonials
    GoCDSpinnaker
    Likelihood to Recommend
    ThoughtWorks
    Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
    Incentivized
    Read full review
    Netflix
    Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
    Incentivized
    Read full review
    Pros
    ThoughtWorks
    • 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.
    Incentivized
    Read full review
    Netflix
    • Fast deployments.
    • Can be integrated with a good variety of other products.
    • Also provides some insights from your environment.
    Incentivized
    Read full review
    Cons
    ThoughtWorks
    • UI can be improved
    • Location for settings can be re-arranged
    • API for setting up pipeline
    Incentivized
    Read full review
    Netflix
    • It does NOT support CFN based deployments
    • Windows based systems finds it difficult to onboard to Spinnaker.
    • Pipeline level access authorisation is not there.
    • Support for EBS volume encryption is probably missing.
    • Attach/detach EBS volumes during deployments is difficult.
    • No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
    • Open-source - so good and bad!
    • Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
    • User authentication is easy but authorisation management is not straight forward.
    Incentivized
    Read full review
    Alternatives Considered
    ThoughtWorks
    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 input the parameters.
    Incentivized
    Read full review
    Netflix
    • Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding
    Incentivized
    Read full review
    Return on Investment
    ThoughtWorks
    • 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
    Incentivized
    Read full review
    Netflix
    • By using Spinnaker we are able to deploy new versions of our product quickly.
    • A deployment takes in average 2 minutes.
    • Our investment on Spinnaker was just time learning it.
    Incentivized
    Read full review
    ScreenShots