What users are saying about
5 Ratings
34 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.1 out of 100
5 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.2 out of 100

Attribute Ratings

  • AWS CodePipeline and GoCD are tied in 1 area: Likelihood to Recommend

Likelihood to Recommend

9.0

AWS CodePipeline

90%
8 Ratings
9.0

GoCD

90%
2 Ratings

Usability

9.0

AWS CodePipeline

90%
1 Rating

GoCD

N/A
0 Ratings

Performance

7.6

AWS CodePipeline

76%
6 Ratings

GoCD

N/A
0 Ratings

Support Rating

9.1

AWS CodePipeline

91%
4 Ratings

GoCD

N/A
0 Ratings

Ease of integration

8.3

AWS CodePipeline

83%
3 Ratings

GoCD

N/A
0 Ratings

Likelihood to Recommend

Amazon AWS

I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
Read full review

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.
Read full review

Pros

Amazon AWS

  • It is reliable and works without errors
  • It integrates well with our repository and all other AWS functions as well as our end database
Read full review

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.
Read full review

Cons

Amazon AWS

  • Ease of use - things like CircleCI or other tools are a bit easier to learn.
  • Ability to build from more sources.
Read full review

ThoughtWorks

  • UI can be improved
  • Location for settings can be re-arranged
  • API for setting up pipeline
Read full review

Pricing Details

AWS CodePipeline

Starting Price

$0

Editions & Modules

AWS CodePipeline editions and modules pricing
EditionModules
Free TierFree1
AWS CodePipeline12

Footnotes

  1. none
  2. per active pipeline/per month

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up fee?

No setup fee

Additional Details

GoCD

Starting Price

Editions & Modules

GoCD editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    Usability

    Amazon AWS

    Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
    Read full review

    ThoughtWorks

    No answers on this topic

    Performance

    Amazon AWS

    AWS CodePipeline only speeds the delivery of code, it does not slow down any other used software and integrates perfectly with other tools. Although it is a web-based tool, it has great performance and compatibility. Besides that, it is greatly enhanced by the other tools of AWS. It is not only limited to AWS tools but can be used with other tools such as GitHub, Jenkins, etc.
    Read full review

    ThoughtWorks

    No answers on this topic

    Support Rating

    Amazon AWS

    We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
    Read full review

    ThoughtWorks

    No answers on this topic

    Alternatives Considered

    Amazon AWS

    CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.

    CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.

    Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.
    Read full review

    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.
    Read full review

    Return on Investment

    Amazon AWS

    • CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
    • CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
    • CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.
    Read full review

    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
    Read full review

    Add comparison