Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
CircleCI
Score 9.5 out of 10
N/A
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.
Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because …
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. …
My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
Based on the fact we are Microsoft shop, it makes sense and it has an great integration to RM for code release. At the time it was the best decision for what we needed as a team. If it were up to me, moving to Git would be the right direction. It is less costly and it is …
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…
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 …
While SVN comes with basic functionalities, TFS is a superior tool and often unused to its potential in most cases. GitHub brings that equilibrium. It perfectly works like a versioning tool and can also be used to create CICD deployment pipelines.
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 at least as good as Bitbucket, if not a little more refined. GitHub is hands-down better than TFS. If you are using TFS, you really need to move to a modern source control system. The newer Azure DevOps Server has a decent Git offering, but the UX is incredibly …
Microsoft Team Foundation Server was too heavy and too complex for fast dvelopment. The integration with opensource build solutions (i.e jenkins) was not explored but the main feedback on this tool was its complexity. CVS and SVN used to be standards in past years and fit …
Git and GitHub are so much easier to use. I didn't necessarily find the others that I've tried difficult, but they all had their quirks. GitHub has their quirks, but their quirks make sense once you really think about i. The other may or may not have command line options, …
Bitbucket actually allows you to integrate with GitHub which is a nice feature. But if you are into the Atlassian suite (JIRA, Confluence, etc.) then Bitbucket might be a no brainer as they work together better. GitHub allows you to have a free wiki whereas with Bitbucket that …
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 …
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
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.
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.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
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.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
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.
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.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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.
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
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.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
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.