CircleCI 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
SourceForge
Score 9.8 out of 10
N/A
SourceForge is a B2B software discovery platform, featuring 4000+ categories in its comparison engine that potential buyers can use to compare software by user reviews, features, pricing, integrations, operating system, and deployment.
N/A
TeamCity
Score 6.8 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
Circle was the first CI with simple setup, great documentation, and tight integration with GitHub. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
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 …
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.
I recommend SourceForge to anyone or business that needs both commercial and open source software. This platform has a wide variety of software with many categories that allow easy search for any project, in addition to the fact that searches can be done separately (commercial and open source software) so as not to have mixed results which go with different purpose. In addition to the fact that the community of this platform is quite active and that there are always times to discover new projects that can be useful for a company or individual person.
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.
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.
The overall design that SourceForge has really leaves a lot to be desired, although the entire platform works perfectly, I think that the design should be much more attractive.
There is currently no feature to save your progress on a review you are writing, so if you are writing a review and the browser is closed for some reason, all progress of the written review will be lost.
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.
Souceforge was very straightforward and easy to manage. The leads worked for us so there is not a lot else to say about why I'd use it again. This isn't some complicated software product, it is a simple inbound marketing channel that is meant to generate leads and help us with brand awareness and it did exactly that.
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.
SourceForge is super easy to use and very intuitive. And their support team and campaign managers help whenever we need it. Using SourceForge as a user is easy, and administrating a business software listing is easy as well. They also have great documentation.
We've never had any issues or downtime with SourceForge. Since we've been a user, the platform has never been down. Or at least never that I've noticed.
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.
SourceForge loads extremely quickly whether you're using the front end or administrating your product listing on the back end. All pages are snappy to load--no issues with page speed whatsoever.
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.
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.
I hardly ever use the support on SourceForge, as I have not needed it. Their product works well for me. One time I had to email them and they got back to me the same day, but that's my only experience.
When we first signed up, they pair you with a campaign manager who trained us on how to use the product properly. The product is simple so the training was only about 30 minutes and after that we understood all the features and how to make the most of it. Most of the work came with making a custom landing page and building a follow up process for our sales team.
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.
G2 has a larger commitment time upfront and for a more expensive rate, which wasn't the best option for our team as we were just exploring the resources that existed out there at the time. We preferred Sourceforge as well due to its subscription service, making it easier to commit from the start.
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.
SourceForge has been plenty scalable for us. Our marketing department is able to edit listings and our executives can also log in to the platform if need be for leads and reporting information. SourceForge offers multiple user access and role permissions, so it's pretty scalable and easy to use for our entire team.
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.
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.
