Codeship vs JFrog Pipeline vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Codeship Logo
139 views|105 comparisons
JFrog Logo
303 views|280 comparisons
100% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Codeship, JFrog Pipeline, and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,578 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pricing and Cost Advice
Information Not Available
  • "The pricing is the cheapest compared to the other platforms out there."
  • More JFrog Pipeline Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,578 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Ask a question

    Earn 20 points

    Ask a question

    Earn 20 points

    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it… more »
    Ranking
    29th
    out of 41 in Build Automation
    Views
    139
    Comparisons
    105
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    22nd
    out of 41 in Build Automation
    Views
    303
    Comparisons
    280
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Jenkins logo
    Compared 52% of the time.
    Bamboo logo
    Compared 14% of the time.
    Harness logo
    Compared 14% of the time.
    GitHub Actions logo
    Compared 9% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 6% of the time.
    Also Known As
    Shippable
    Learn More
    Overview
    Codeship is a fully customizable Continuous Integration Platform with native Docker support. Codeship gives you complete control over customizing and optimizing you CI and CD workflow. Choose which steps should run sequentially or in parallel, how many concurrent builds you want to run simultaneously among your account and get full control over which dependency version you want to run for each step or when to delete your dependencies and the cache. Codeship can provide complete developer autonomy. If you can run it in a Docker container, Codeship can run it for you.
    JFrog Pipelines empowers software teams to ship updates faster by automating DevOps processes in a continuously streamlined and secure way across all their teams and tools. Encompassing continuous integration (CI), continuous delivery (CD), infrastructure and more, it automates everything from code to production. Pipelines is natively integrated with the JFrog Platform and is available with both cloud (software-as-a-service) and on-prem subscriptions.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    Sample Customers
    Product Hunt, Bannerman, LendingCrowd, GameHouse Promotion Network, Mixcloud, qunb, Usetrace, Frontback
    SAP, Today Tix, Cisco, Lithium, Pushspring, Packet
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    No Data Available
    No Data Available
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company9%
    Comms Service Provider7%
    Company Size
    No Data Available
    No Data Available
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,578 professionals have used our research since 2012.