Our teams are being asked to move from self-managed GitLab to Azure DevOps on-premises. The GitLab platform and runners currently run on Kubernetes, and we're mainly a .NET shop. What challenges should we look into before committing to the move?
What should we expect moving from self-managed GitLab to Azure DevOps on-prem?
Answers
First, get a clearer reason for the move than just less friction with .NET. Ask which specific builds, integrations, or maintenance problems it is supposed to improve, then test those against the current setup.
A .NET shop doesn't necessarily need Azure DevOps to build and deploy .NET applications. The migration has a cost, so there should be a concrete benefit worth comparing against it.
Reply to this answer
Check the exact Azure DevOps Server version against the SDKs, build tasks, and agents you need. The on-prem product can lag the cloud service, so don't assume a task documented for the cloud will work the same way on your server.
Make a small test pipeline for your newest .NET version and another for your oldest supported app. Include restore, build, test, packaging, and deployment rather than stopping once the code compiles. Also check the server and agent update process with whoever will maintain it.
Reply to this answer
The Kubernetes setup deserves its own proof of concept. GitLab runners and Azure DevOps agents aren't interchangeable, so map out how agents will be deployed, configured, updated, and given access to the resources your builds need.
Try a representative pipeline with its secrets, dependencies, and deployment targets. That should expose the operational work involved in replacing the runner setup, not just the effort of rewriting pipeline definitions.
Reply to this answer
Azure DevOps can do the job, particularly if your team is comfortable with PowerShell and the .NET ecosystem. Still, check the integrations you rely on today rather than assuming they have equivalent support on-prem.
Inventory more than repositories and builds. Work tracking, permissions, and deployment workflows are worth checking too. Pick a project with a few real dependencies for the pilot so you can see where the gaps are before moving everyone.
Reply to this answer
Add your answer
Answers are reviewed before publication.
2d~socketrivet_487:
Checking the specific server release matters here. General claims that the product is dead don't tell you whether your required tasks and agents are supported.