CircleCI vs. SourceForge vs. Travis CI

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

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.

TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.

Incentivized

• 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

• Commercial software and FOSS projects are available.
• FOSS projects have advanced profiles such as software hosting for download as well as download metrics. As well as the released versions.
• Commercial software profiles show detailed features, what it offers, price, frequently asked questions and a vast amount of user reviews.

• It is very simple to configure a range of environment versions and settings in a simple YAML file.
• It integrates very well with Github, Bitbucket, or a private Git repo.
• The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.

Incentivized

• 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

• 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.

• I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
• There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.

Incentivized

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.

Incentivized

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.

TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.

Incentivized

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.

Incentivized

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.

Incentivized

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.

After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.

Incentivized

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.

We have used this service mainly to read explicit opinions that influenced the decision-making when implementing new software for my company

Incentivized

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

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.

Incentivized

Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not worth the trouble. Codeship supports integration with GitHub, GitLab and BitBucket. I've only used it briefly, but it seems to be a nice tool.

Incentivized

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.

Incentivized

• It allowed us to learn more about the features and functions of some software that we currently use.
• It allowed me to improve my decision-making for the software we use in the project area.
• It helped us to replace several programs that were used in our company. We made several replacements, for much more optimal alternatives.

• It's improved my ability to deliver working code, increasing my development velocity.
• It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
• It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
• It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
• The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".

Incentivized