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
GitHub
Score 9.1 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
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.
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 …
We use CircleCI when we need a good, independent CI/CD provider in an existing workflow. That said, we've begun investing more heavily in GitHub actions as it's closer to where our code is stored. CircleCI is a feature of a workflow, and can be filled by many different service …
Based on the cost for feature set that we needed we went with CircleCI. There were also more people on our team that knew how to use CircleCI already compared to other products which made it a preferred choice for ramp up. Other products were not as robust and quick to …
While the UI on CircleCI is not my favorite, it's leagues better than Travis CI. I really like Heroku CI much better, but the functionality is much more limited there. If Heroku CI had the same functionality as CircleCI, I probably wouldn't use 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 …
It was our CTO who did the evaluation, not me, but as I recall other services weren't as parallelizable. We knew we wanted to run on many containers simultaneously for fast test results.
For us it really came down to CricleCI being the fastest and simples tool to get started with. The GitHub integration is slick and seamless and the scripting config file allowed us to configure our entire build system, including tests, in less than a day. It's very light weight …
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 …
The biggest downside to CircleCI is that it doesn't support parameterized builds, that is testing your code against language version X and Y, or framework version A and B. Beyond that, it is really a great product.
I had used Travis CI in some of my open source projects. However, it was too expensive for us so I looked for an alternative that was in our budget. Scrutinizer is also very useful, but also out of our budget. When we get larger I could see myself using Scrutinizer for quality …
I think these three tools are just as good as the other except that Travis CI supports mobile a lot better but price wise, CircleCI is the best that I have found and is supports the need for a startup. For a long while, CircleCI had Docker support before Codeship but now, Codesh…
SourceForge has been adulterating binaries and installers, bundling crapware/adware. These practices are incredibly questionable at best, and in my mind, nothing from the site is to be trusted anymore.
Github and git, in general, is much better than SVN or Subversion for version tracking and code collaboration. It takes the best parts of SVN and fixes a lot of what was broken with it. Github's own UI has evolved really well over time and they have taken developer productivity …
We picked GitHub because it's what I was most familiar with when we started. We're testing out self-hosted Gitlab because it not only handles all the features we're using on GitHub, but it also has a continuous integration service which is currently implemented by a third party …
Github is the clear industry leader in collaborative software development -- we use it because it has superior tooling, integrations with third parties, and hosts a lot of the open source code that we use every day. Bitbucket is a better fit for organizations that are deeply …
GitHub is like an end to end solution compared to Bitbucket from Atlassian. With regards to defect tracking in Git, professionals are comparing it with the likes of Jira. Also the newly added features of social networking make it a unique tool to connect with like minded …
Others not listed above, CVS, Microsoft SourceSafe. GitHub offers the most comprehensive offering, including Code Review, Open API, Wiki (just to mention a few) in a single package. GitHub is likely the most used repository in the world. It's fast, even with high user volume. …
In my opinion, GitHub beats all of the competition.
The other services offer some things that could be considered benefits in some scenarios: Bitbucket has good integration with other Atlassian products, Gitlab is self-hosted and completely free, Beanstalk integrates with some …
Local storage of your repository is not exactly the safest thing you should do, since if you lost your project, you lose your project. This is not really a great alternative when you are considering it over using some thing you can access from any computer at any time. GitHub …
G2 lacks the open-source community like SourceForge and does not allow interaction between developers and customers, although both do a commendable job of listing useful business and open-source software along with their price comparisons and reviews.
I use SourceForge because here you can easily filter out and find the right software, and it has a huge collection of open-source software with trustworthy reviews.
Verified User
Employee
Chose SourceForge
I just think SourceForge is the best for a person who's not really interested in the code but only wants a trustworthy way to read about and decide which software to use.
Features
CircleCI
GitHub
SourceForge
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
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.
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
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.
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.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
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.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
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.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
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.
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.
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
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.
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
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.
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.
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.