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

    Red Hat OpenStack Platform

    Score7.5 out of 10
    N/ARed Hat OpenStack Platform is a cloud computing platform that virtualizes resources from industry-standard hardware, organizes those resources into clouds, and manages them so users can access what they need—when they need it.N/A
    Pricing
    GoCDRed Hat OpenStack Platform
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    GoCDRed Hat OpenStack Platform
    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
    GoCDRed Hat OpenStack Platform
    Small Businesses
    Apache Maven
    Score9.1 out of 10
    No answers on this topic
    Medium-sized Companies
    Apache Maven
    Score9.1 out of 10
    No answers on this topic
    Enterprises
    Gradle Build Tool (Open Source)
    Score9 out of 10
    No answers on this topic
    All AlternativesView all alternativesView all alternatives
    User Ratings
    GoCDRed Hat OpenStack Platform
    Likelihood to Recommend
    9.0
    (2 ratings)
    8.0
    (1 ratings)
    User Testimonials
    GoCDRed Hat OpenStack Platform
    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
    Red Hat
    Best suited for - any organization where you have people who already have expertise on OpenStack, Linux & IP networking. Otherwise, the maintenance & operations will be difficult. When the number of deployed VMs reaches its capacity, it becomes very difficult to manage Red Hat OpenStack because there are no in-built fault management & performance management tools available within Red Hat OpenStack. Not suited for - Organizations where people have a culture of working on automated GUI-based tools. Here VMware wins over Red Hat OpenStack. Also where you have mission-critical applications where downtime cannot be tolerated.
    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
    Red Hat
    • Scaling of application components (VMs).
    • Managing the networking between virtual machines.
    • Management of VNFs & the underlying infrastructure.
    • Availability & uptime of VMs because of features like VM migration & evacuation.
    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
    Red Hat
    • User management really needs improvement - when compared to AWS or GCP.
    • Security of the overall platform needs to be improved.
    • The whole architecture needs to be modular which is not. Ex - Upgrading any particular component (nova, neutron, cinder) should be possible without upgrading the whole Red Hat OpenStack version.
    • The creation of HEAT templates for complex applications is still a challenge & has a dependency on external tools.
    • Stack creation still requires parameters modification at controllers & compute because of the complex nova-scheduler algorithm.
    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
    Red Hat
    Only because of low cost & zero licensing of Red Hat OpenStack
    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
    Red Hat
    • Saved CAPEX for sure (I can't quote a figure).
    • Saved Opex also - because a large support community is already available.
    • Increased complexity of system setup though.
    Incentivized
    Read full review
    ScreenShots