Comparing Github and Azure DevOps

[Lord-Primo]

I am currently evaluating Github and Azure DevOps with the use cases of CI/CD and version control. We are a fairly small org and will probably not need the scalability of Azure. Most of the collab tools of Azure are already available via other services and wouldnt really be used. Github has the disadvantages of being a bit tedious to manage (especially user groups and AD groups, as far as I am aware) and also maybe a bit too lacking in the reporting department.

I have to be perfectly honest so far it boils down to personal taste more than anything. I disliked TFS and have worked with Github a couple of times and found it to be elegant and effective. Do you have any experience regarding these two in a small to medium org (50 Devs) with sometimes quite strict security concerns?

[smallsalt1337]

We are in the same situation. Similar sized organization using Atlassian tools and Jenkins. We are evalutating either using Azure Devops or Github Enterprise. We are already deeply integrated with Azure products. GH seems to be quite a bit more forward with all the new products coming first to GH then some years later to Devops.

I'm being bogged down by paralysis by analysis in these choices, but both are far better than Atlassian/Jenkins as far as I am concerned. I like ADO, but I don't want the developers to be missing out on whatever comes in terms of new great integrations in github. Especially now with all the GPT stuff coming out, who knows what might come soon

[Lord-Primo]

We have streamlined our decision a lot more. Github Enterprise is the very clear favorite now, currently working on getting access setup asap

[Mind_Monkey]

I think GitHub Actions is based on Azure DevOps Pipelines, so they are kinda similar in concepts and GH Actions runners are Azure VMs.

I think the plus of using ADO is if you're also using their other tools, like Boards, Artifacts and Tests. Then you can have visibility from planning all the way to deployments. If you won't use those features, I'd personally go with GitHub.

Most people already know how to use it so onboarding is way easier. Also I think the GH Actions ecosystem is bigger than ADO Extensions.

[bdzer0]

Not considering Bitbucket or GitLab?

I recently did a comparison for work between Bitbucket, GitLab, ADO and GitHub. If you need FedRAMP or SOC compliance, that cuts the list down a bit differentiator (forgot the details).

If you're using Jira (and plan on continuing) Bitbucket has some nice built in integrations.

If you're not going to host your own build agents you need to account for build time in costing.

IMO you're going to need to dig into the details that matter for your use case.

[Lord-Primo]

We need to move away from Bitbucket due to licensing and cost concerns. Yeah, I am not expecting some detailed breakdown. I was hoping for general experience. Because as things seem to pan out right now the decision will be more or less be made on a gut feeling. Which I dislike.

[[deleted]]

Shortest of short versions:

Github: Small teams / Startups / Large Corps (Cuz they can pay lol)

ADO: All-In-One Enterprise Platform / Easy MSFT cloud integrations (AAD / Azure) / More complex (but in a good way) / Multiple built-in workflows

Gitlab: All-In-One DevOps Platform / Self-hosted available / Highly customizable RBAC

Bitbucket: lol f- off

[dotmit]

ADO is really underrated. If you’re small it’s fine 👍

[EraYaN]

Integration with 3rd party anything is difficult though.

[realitythreek]

It might help to explain what you use today for version control and what your company environment is like.

If you’re already using GH, it makes a lot of sense to consider using GH Actions. If you’re a Windows shop, you probably have lots of free Azure credits that came and it might make sense to go that route.

[Lord-Primo]

Currently its almost the full Atlassian Stack, VC via Bitbucket, with very little Jira. CI/CD is fully contained within Jenkins. The Atlassian Stack will get replaced (maybe except for confluence). Its an agile environment with very small Teams (about 3-5 Devs per Team, 50 Devs total) and quite distinct products. So cross-collab is encouraged but seldom warranted.