TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    AWS CodePipeline

    Score6.6 out of 10
    N/AAWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model a user defines.

    $1

    per active pipeline/per month

    Jenkins

    Score8.1 out of 10
    N/AJenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A

    TeamCity

    Score7.1 out of 10
    N/ATeamCity is a continuous integration server from Czeck company JetBrains.N/A
    Pricing
    AWS CodePipelineJenkinsTeamCity
    Editions & Modules
    AWS CodePipeline
    $1
    per active pipeline/per month
    Free Tier
    Free
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    AWS CodePipelineJenkinsTeamCity
    Free Trial
    NoNoNo
    Free/Freemium Version
    YesYesNo
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details———
    More Pricing Information
    Community Pulse
    AWS CodePipelineJenkinsTeamCity
    Considered Multiple Products
    Amazon AWS
    Chose AWS CodePipeline
    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 …
    Incentivized
    Chose AWS CodePipeline
    We selected AWS CodePipeline mainly because we wanted to keep the application stack completely native to AWS, and CodePipeline provided the best integrations with AWS services that we were using, such as S3, Elastic Beanstalk, and Lamba. Furthermore, AWS CodePipeline provided …
    Incentivized
    Chose AWS CodePipeline
    AWS Codepipeline is proprietary to Amazon Web Services and works well when you're working with other AWS products. If you're using a different technology stack, then Codepipeline may not be the best tool and some open source/closed source tools available on the web may suffice.
    Incentivized
    Chose AWS CodePipeline
    We selected CodePipeline again, because it integrates well with our AWS Based infrastructure.
    Incentivized
    Chose AWS CodePipeline
    They all pretty much have the same feature set. AWS CodePipeline has been improving in recent years, and it just makes sense to keep everything within Amazon's ecosystem.
    Incentivized
    Chose AWS CodePipeline
    I felt that, out of the alternatives, AWS CodePipeline was the simplest to setup and most reliable. Since my client's infrastructure was already hosted in AWS, I felt it was a no-brainer. If a client needed a similar solution with on-prem or non-AWS infrastructure, I would …
    Incentivized
    Open Source
    Chose Jenkins
    Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
    Incentivized
    Chose Jenkins
    When looking for alternatives for Jenkins we found CircleCI and TeamCity are good too. Jenkins was considered for reasons like it has a wide variety of plugins which integrate well with any kind of system. And its ease of use.

    One of the other greater advantage is it is open …
    Incentivized
    Chose Jenkins
    TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCi…
    Incentivized
    Chose Jenkins
    I would use TeamCity if Jenkins was not already in place. TeamCity seems a lot more stable when it comes to upgrading the software and job templates the way TeamCity handles them is an absolute killer feature. Jenkins is a bit of a wild animal, quite unpredictable but with the …
    Incentivized
    Chose Jenkins
    Jenkins is ideal for developing software with high-security demands. It is hosted and set up locally and has no outside connections. But these pros could become cons when you work on open source projects and need to waste time for initial setup and maintenance over a project's …
    Incentivized
    Chose Jenkins
    I just started to use TeamCity so later I can give you a better comparison.
    Incentivized
    Chose Jenkins
    I have experience with TeamCity. It looks pretty good after Jenkins, the user interface is friendly and modern. The functionality is similar to Jenkins. It is not a big problem to migrate configuration from Jenkins to TeamCity or to return back. You need licenses to use it in …
    Incentivized
    Chose Jenkins
    Jenkins is very easy to use, open source tool. Its better for simple build and deployments.
    Incentivized
    Chose Jenkins
    Originally Jenkins was selected because it was the best around, but it has since been outclassed by more specific services or cloud-based services and tools that will do all of the heavy lifting for you. Jenkins still has a use case - but it's hard to argue the additional …
    Incentivized
    Chose Jenkins
    Jenkins is the only tool I would consider using for CTCI deployment. Its plugins make it easy to customize to any environment you can conjure up and will always be custom fit to your needs as a DevOps engineer. Other tools have better support but lack the customizability and …
    Incentivized
    Chose Jenkins
    It is free, of course that's the best advantage. Great number of plugins. Largest active developer community among peer competitors. Very few competitors have got the pipelines features right as good as Jenkins.
    Incentivized
    Chose Jenkins
    Jenkins is open source and gives flexibility of integrating it with various products and platforms.
    Incentivized
    Chose Jenkins
    Unfortunately I can't weight on decision making points since selection of Jenkins was made prior to me joining the company.
    Incentivized
    Chose Jenkins
    I've used these others as well:
    TeamCity
    - has master slave concept but master is also not load balance-able like Jenkins.
    Incentivized
    JetBrains
    Chose TeamCity
    Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find …
    Incentivized
    Chose TeamCity
    Since we were already making use of other JetBrains offerings, TeamCity had a leg up on the competition due to the ease of integration with these tools. With that said, TeamCity's feature set stacks up well with the competition. Jenkins definitely has some nice features, but …
    Incentivized
    Chose TeamCity
    Jenkins and Team Foundation Server (TFS) are both strong products. Compared to Jenkins, TeamCity is much more mature and polished. Though Jenkins is open-source/free, the cost of TeamCity is a drop in the bucket compared to the total cost of even one project we're using it …
    Incentivized
    Chose TeamCity
    TeamCity is more easy to use and configurated easily.
    Incentivized
    Chose TeamCity
    This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose …
    Incentivized
    Chose TeamCity
    I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, …
    Incentivized
    Chose TeamCity
    TeamCity by far has the best interface TeamCity still supported our old SubVersion reports as well.
    Incentivized
    Chose TeamCity
    I like the quality of Jetbrains products. TeamCity is well supported and regularly updated by Jetbrains. They have an active support forum and most questions are answered quickly.

    TeamCity is very extendable and has been able to handle everything we've been required to do.
    Incentivized
    Chose TeamCity
    TeamCity is the best combination of price and full features. It has a good web UI and doesn't need a lot of manual configuration files, but it still is incredibly extensible and can do just about any build or release task you set it at. If it can't do it, the odds are it has a …
    Incentivized
    Chose TeamCity
    • Easy implementation.
    • Cleaner dashboard and UI.
    • Better documentation and tutorials.
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    87%
    Would buy again
    26 Answers
    100%
    Would buy again
    5 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    27 Answers
    No answers on this topic
    Happy with the feature set
    No answers on this topic
    87%
    Happy with the feature set
    26 Answers
    100%
    Happy with the feature set
    5 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    93%
    Lived up to sales and marketing promises
    13 Answers
    No answers on this topic
    Implementation went as expected
    No answers on this topic
    96%
    Implementation went as expected
    22 Answers
    No answers on this topic
    Best Alternatives
    AWS CodePipelineJenkinsTeamCity
    Small Businesses
    CircleCI
    Score9.2 out of 10
    Apache Maven
    Score9 out of 10
    Apache Maven
    Score9 out of 10
    Medium-sized Companies
    CircleCI
    Score9.2 out of 10
    Apache Maven
    Score9 out of 10
    Apache Maven
    Score9 out of 10
    Enterprises
    CircleCI
    Score9.2 out of 10
    Gradle Build Tool (Open Source)
    Score9 out of 10
    Gradle Build Tool (Open Source)
    Score9 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    AWS CodePipelineJenkinsTeamCity
    Likelihood to Recommend
    9.0
    (8 ratings)
    6.7
    (74 ratings)
    10.0
    (18 ratings)
    Usability
    9.0
    (1 ratings)
    6.4
    (8 ratings)
    -
    (0 ratings)
    Performance
    6.8
    (2 ratings)
    8.9
    (6 ratings)
    9.3
    (2 ratings)
    Support Rating
    9.1
    (2 ratings)
    6.6
    (6 ratings)
    -
    (0 ratings)
    Implementation Rating
    -
    (0 ratings)
    6.0
    (1 ratings)
    -
    (0 ratings)
    Ease of integration
    7.4
    (2 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    User Testimonials
    AWS CodePipelineJenkinsTeamCity
    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.
    Incentivized
    Read full review
    Open Source
    Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
    Incentivized
    Read full review
    JetBrains
    TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
    Incentivized
    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
    Incentivized
    Read full review
    Open Source
    • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
    • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
    • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
    Incentivized
    Read full review
    JetBrains
    • TeamCity provides a great integration with git, especially Bitbucket.
    • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
    • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
    Incentivized
    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.
    Incentivized
    Read full review
    Open Source
    • The UI could be slightly better, it feels kind of like the 90s, but it works well.
    • An easier way to filter jobs other than views on the dashboard.
    • An easier way to read the console logs when tests do fail.
    Incentivized
    Read full review
    JetBrains
    • The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
    • Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
    Incentivized
    Read full review
    Likelihood to Renew
    Amazon AWS
    No answers on this topic
    Open Source
    We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
    Incentivized
    Read full review
    JetBrains
    No answers on this topic
    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.
    Incentivized
    Read full review
    Open Source
    Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
    Incentivized
    Read full review
    JetBrains
    No answers on this topic
    Performance
    Amazon AWS
    Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
    Incentivized
    Read full review
    Open Source
    No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
    Incentivized
    Read full review
    JetBrains
    TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
    Incentivized
    Read full review
    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.
    Incentivized
    Read full review
    Open Source
    As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
    Incentivized
    Read full review
    JetBrains
    No answers on this topic
    Implementation Rating
    Amazon AWS
    No answers on this topic
    Open Source
    It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
    Incentivized
    Read full review
    JetBrains
    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.
    Incentivized
    Read full review
    Open Source
    Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
    Incentivized
    Read full review
    JetBrains
    TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
    Incentivized
    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.
    Incentivized
    Read full review
    Open Source
    • Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement.
    • Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards.
    • Cost Savings: Jenkins is an open-source tool that is free to use
    Incentivized
    Read full review
    JetBrains
    • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
    • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
    • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
    Incentivized
    Read full review
    ScreenShots