TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    CircleCI

    Score9.3 out of 10
    N/ACircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.

    $0

    for up to 6,000 build minutes and up to 5 active users per month

    Git

    Score10 out of 10
    N/AN/AN/A
    Pricing
    CircleCIGit
    Editions & Modules
    Server
    Contact Sales
    Performance
    starting at $15
    per month
    Scale
    starting at $2000
    per month
    No answers on this topic
    Offerings
    Pricing Offerings
    CircleCIGit
    Free Trial
    NoNo
    Free/Freemium Version
    YesNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Community Pulse
    CircleCIGit
    Considered Both Products
    CircleCI
    Chose CircleCI
    Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.

    Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at …
    Incentivized
    Open Source
    Chose Git
    Git is my favorite among all of the version control systems out there. It follows the Linux software philosophy of being built by many loosely coupled and small components that do one thing well. It's incredibly open, and its adoption in the open source community seems to be …
    Incentivized
    Key User Insights
    Would buy again
    100%
    Would buy again
    8 Answers
    100%
    Would buy again
    12 Answers
    Delivers good value for the price
    100%
    Delivers good value for the price
    8 Answers
    100%
    Delivers good value for the price
    11 Answers
    Happy with the feature set
    100%
    Happy with the feature set
    8 Answers
    100%
    Happy with the feature set
    12 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    5 Answers
    100%
    Lived up to sales and marketing promises
    9 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    7 Answers
    100%
    Implementation went as expected
    9 Answers
    Best Alternatives
    CircleCIGit
    Small Businesses
    No answers on this topic
    GitHub
    Score9.2 out of 10
    Medium-sized Companies
    AWS CodePipeline
    Score6.6 out of 10
    GitHub
    Score9.2 out of 10
    Enterprises
    AWS CodePipeline
    Score6.6 out of 10
    Perforce P4
    Score7.5 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    CircleCIGit
    Likelihood to Recommend
    9.0
    (27 ratings)
    10.0
    (36 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    10.0
    (1 ratings)
    Usability
    9.0
    (2 ratings)
    9.0
    (1 ratings)
    Performance
    7.8
    (3 ratings)
    -
    (0 ratings)
    Support Rating
    6.9
    (6 ratings)
    8.5
    (11 ratings)
    Implementation Rating
    -
    (0 ratings)
    9.0
    (1 ratings)
    User Testimonials
    CircleCIGit
    Likelihood to Recommend
    CircleCI
    Based on our experience, CircleCI is well-suited for automating mobile app release cycles. For example, to release an iOS app, you would need to build, sign, and upload it to TestFlight, which requires a dedicated Mac in the office. But with CircleCI, you can have macOS executors, so you don't have to manage a physical build machine. Another benefit is that CircleCI's certified AWS Orbs abstract away complex authentication and deployment logic, allowing us to build, push, and deploy Docker containers to Amazon ECS with minimal configuration and high reliability. CircleCI is less suited for smaller projects where the development and deployment are not that extensive, for example, a static site. Once you have built a static site, you probably won't make any further changes, so there's no point in paying for it.
    Incentivized
    Read full review
    Open Source
    GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
    Incentivized
    Read full review
    Pros
    CircleCI
    • Automated builds! This is really why you get CircleCI, to automate the build process. This makes building your application far more reliable and repeatable. It can also run tests and verify your application is working as expected.
    • Simple. Unlike Jenkins, Teamcity, or other platforms, CircleCI doesn't need a lot of setup. It's completely hosted, so there's no infrastructure to set up. The config file does take a bit to understand, but if you follow their example and start with something small and add to it, you can get it up and going quicker than it first looks.
    • Scales easily. Again, since it's all cloud-based, you don't have to manage or scale infrastructure. Simply subscribe to the number of containers you want, and scaling up just means buying more containers.
    Incentivized
    Read full review
    Open Source
    • Ability to create branches off current releases to modify code that can be tested in a separate environment.
    • Each developer had their own local copy of branches so it minimizes mistakes being made.
    • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
    • Conflicts are displayed nicely so that developers can resolve with ease.
    Incentivized
    Read full review
    Cons
    CircleCI
    • While configuration is easy, the config files can get very very long.
    • Price compared to some alternatives that are cheaper / free. Especially so if you are running multiple containers in parallel.
    • Have experienced numerous outages (3-5) in the last few months where CircleCI has been down.
    • Web documentation and tutorials haven't been as good as some of the competitors.
    Incentivized
    Read full review
    Open Source
    • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
    • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
    • Many different GUIs, many people (including myself) opt to just use the command-line.
    Incentivized
    Read full review
    Likelihood to Renew
    CircleCI
    No answers on this topic
    Open Source
    Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
    Incentivized
    Read full review
    Usability
    CircleCI
    The reliability & speed, it just works. The ability to spin up macOS runners and Docker containers on demand without managing hardware is a huge win. The Orbs system makes integrating with AWS and Slack incredibly easy, saving us weeks of custom scripting and providing real-time updates in our Slack channel. This makes it easy for us to track and ensures that everyone involved knows the status. Of course, it has drawbacks related to configuration complexity and, in some cases, cost transparency, but overall, it is an industry-standard, robust tool that solves our core infrastructure problems well.
    Incentivized
    Read full review
    Open Source
    Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
    Incentivized
    Read full review
    Performance
    CircleCI
    It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
    Incentivized
    Read full review
    Open Source
    No answers on this topic
    Support Rating
    CircleCI
    Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
    Incentivized
    Read full review
    Open Source
    I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
    Incentivized
    Read full review
    Implementation Rating
    CircleCI
    No answers on this topic
    Open Source
    It's easy to set up and get going.
    Incentivized
    Read full review
    Alternatives Considered
    CircleCI
    Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on their infrastructure, and we can configure it from a config file that we track in GitHub.
    Incentivized
    Read full review
    Open Source
    I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
    The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
    It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
    Incentivized
    Read full review
    Return on Investment
    CircleCI
    • We pay over $5K/ month and we have high expectations for service. Sometimes I feel that we don't get the value, but only sometimes.
    • We have had to build our own application to keep state and broker releases and deployments. We call our app deployer. I feel that CircleCI could do more to understand our needs and possibly build additional features that would enable us to invest less in build and deployment infrastructure and justify paying more for Circle.
    Incentivized
    Read full review
    Open Source
    • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
    • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
    • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
    Incentivized
    Read full review
    ScreenShots