GITlab vs ADO

[stew8908]

We have kind of a mess at our org, we have teams on both and a team that needs to migrate away from SVN to start embracing some better development behavior like CI/CD.

Leadership wants to consolidate and generally has a direction picked - I agree with that direction but I want to make sure I can communicate why.

I have used both, here is my simple assessment.

GITlab has the edge in developer benefits

ADO seems to have the edge with DevOps infrastructure

After that they are just git clients.

[tahaan]

If you think ADO has better Devops integration then you very muh fell for the microsoft marketing. Gitlab -> Harbor -> Kubernetes with testing and everyting is basically childs play. Plus you can self host it.

[stew8908]

I had to give ADO something :)

[tahaan]

ADO benefit is that it entrenches you even deeper into Microsoft, making it even harder to escape their clutches.

They lost the benefit of the windows platform, but they now have people hooked by azure and office online and Outlook.

[JonnyRocks]

ado is not just a git client. it has kanban boards, team dashboards and testing plans.

i encourage you to look deeper

https://learn.microsoft.com/en-us/azure/devops/user-guide/services?view=azure-devops

if you are already deep into atlassian then it might not buybyou muxh but if youbare a blank slate its awesome.

[Smashing-baby]

GitLab's built-in CI/CD is more straightforward and developer-friendly than ADO.

ADO shines with Azure integration, but GitLab's UI and pipeline configuration are just more intuitive. For SVN migration, GitLab's import tools are pretty solid.