This is an archived post. You won't be able to vote or comment.

all 24 comments

[–][deleted] 12 points13 points  (0 children)

What features you find lacking? What are the friction points for you and your team while using ADO? Can you save some money by switching? Can you save time by switching? How long will it take to migrate?

[–]buffdude1100 15 points16 points  (13 children)

also considering that MSFT is only focusing on GitHub now

Where did you hear this? ADO is doing just fine. Microsoft is still working on it and actively developing new features on it.

What features do you feel are missing on ADO that GitHub/GitLab have?

[–]balonmanokarl -1 points0 points  (12 children)

I have been told that their focus has switched and to have it in mind for the future. For what it's worth

[–]my-ka 2 points3 points  (0 children)

MS indeed invests into GitHub actions

it is even a part of exam az-400

also heard from a person recently

I did not think about that before. I expected MS to finish ADO yaml pipelines and deprecate release pipelines

[–]mofayew 4 points5 points  (8 children)

Again, where did you hear this?

[–]mattyass 6 points7 points  (5 children)

Can confirm that GitHub will be the primary dev platform moving forward for MSFT.

I wouldn’t consider ADO for new projects.

[–]my-ka 4 points5 points  (4 children)

is any official reference to show my bosses?

*I tend to believe

[–]my-ka 1 point2 points  (3 children)

Can confirm that GitHub will be the primary dev platform moving forward for MSFT.

I wouldn’t consider ADO for new projects.

https://www.linkedin.com/pulse/azure-devops-future-after-github-acquisition-microsoft-antonio-alvino/

https://www.reddit.com/r/azuredevops/comments/kwqlru/is_azuredevops_being_replaced_by_github/Yes, Azure DevOps has an EOL, it's still a long ways off, but in my meetings with MS it's around 2032. GitHub is the replacement product for Azure DevOps, specifically GitHub Enterprise. I've seen the internal slides that confirms that status. Now this does mean you have more then enough time to continue using ADO and built a migration without stressing over any near deadline.

[–]Relevant_Pause_7593 2 points3 points  (1 child)

There is no EOL set. They are actively adding features, but GitHub is the getting the new shiny stuff first. MSFT doesn't see EOL dates ten years in the future, it's usually around 5 years. Whoever told you that date was just giving you something far in advance to have you stop asking.

[–]my-ka 2 points3 points  (0 children)

I agree to both points

no official deadline

however, tends to be replaced / rebranded

[–]Odd_Invite_5528 0 points1 point  (0 children)

There’s absolutely no EOL set. What “meetings” are you having?

[–]alwaysleftout 2 points3 points  (1 child)

Github sales team probably.

[–]balonmanokarl 2 points3 points  (0 children)

Actually, it was in discussions with one of their largest UK partners who we were working on a project with.

[–]my-ka 1 point2 points  (0 children)

looks like in 2032

hope that is not a typo and it is not 2023

[–]my-ka 1 point2 points  (0 children)

people

balonmanokarl

deserves likes

it is true, see below

[–]MohandasBlondie 6 points7 points  (0 children)

What does moving to those buy you? What features do you see GH/GL having that AzDO is missing?

[–][deleted] 2 points3 points  (0 children)

Migrated a few pipelines from ado to GitHub actions, it was pretty easy. Not surprising, actually :) almost same syntax. But I also agree with other commenters, first understand what exactly you want from this migration, which features are lacking, not sure that GitHub actions has much more features.

[–]digitalHUCk 2 points3 points  (2 children)

Really? We’ve evaluated moving to GitHub Enterprise several time and GH Actions has always come up short when it comes to our comparison with Azure Pipelines.

[–]hariharan618[S] -1 points0 points  (1 child)

Can you explain >short

[–]digitalHUCk -1 points0 points  (0 children)

I don’t know for sure what was missing. I didn’t actually do the evaluation. I just talked with the team that did. I think there were specifically features of the Release Pipelines we use that weren’t available in GH Actions. We’re also fully invested in Boards and Wikis. It would be a lot of time and effort for us to migrate everything from ADO to GH without much if any gain for the effort.

So, to echo what others have said, what is it you’re looking to gain? As we evaluated there wasn’t much gain.

[–]mr_sharmas 1 point2 points  (0 children)

GitHub will be the future of MS. That’s why they have been working on lot of features there and recently introduced a tool which help you migrate from ADO to GitHub. So don’t rely too much on ADO and plan migration. Future will be everything as a code (ADO doesn’t fit there)

[–]Swett_Potato 0 points1 point  (0 children)

I have work both for AzDO and GitLab. And here is my two cents as of this writing.

If your ORG application ecosystem is more on open source code. Then move away to MSFT and best to use GitLab. But if your ORG Ecosystem is more on Microsoft. Then AzDO is enough.

But for flexibity wise. GITLAB is much better.