Printable View
I would guess that somebody on here has some experience with this. I have none.
My group is being asked to move to this as a source repository. Prior to this, we've been using GitLab, but there are a couple reasons why we have been asked to move, most of which may be bureaucratic in nature (in other words, no good reason). I haven't had a chance to take a good look at this. Can I get some discussion on what issues we are likely to run into?
The only real experience I have with the Azure platform is with their storage service. I wrote a back-up program some years ago that backs up files as binary blobs in Azure containers. This is the extent of my experience with Azure so far. Haven't looked into DevOps so I can't speak on that.
From a pure code repo point of view there will be very little difference to Gitlab - it is just another git repo at the end of the day. In fact Azure DevOps can import an existing repo (all branches, history etc) with a couple of mouse clicks...Quote:
Originally Posted by Shaggy Hiker
If you have been using other features of GitLab such as portfolios, artifacts, etc. then moving them over might be more of an issue.
I have been working with azure devops for quite some time, and from a professional point of view, there are much more advantages. You can use any language, any platform, and any cloud, get more faster delivery and go-live for user services.
I would advise you to read different cases of real use in practice https://www.altoros.com/portfolio/di...r-construction, this will give a more detailed view. I think you can figure it all out for yourself. Good luck:)