Well, the last paragraph of your article makes clear you have no idea about what you're saying.
Az DevOps is used by all engineering teams in Microsoft, just to mention the Windows Universal Platform (Windows, Xbox Live and other products) dev team has ~22k developers with ~500Gb of source code, so to support this size of project, Microsoft created a Virtual Filesystem for Git (github.com/Microsoft/VFSForGit/blo...).
Despite this one, there are tons of other use cases, even the Az DevOps team which generates thousands of the builds daily as well as office team which generates 7Tb of pdb files stored in Az DevOps for production debuging purposes.
Sorry but if you don't know how to use Az DevOps, it is not a problem of the product, but yours.
Sincerely, Luciano.
I don't care if Microsoft is dog-fooding their own product, as an outsider and someone who's used and built similar products, Azure DevOps has given me a bad user experience. It does't matter if the employees are using the product (they probably don't have choice anyway), at the end of the day they have to sell it and I definitely won't buy it. And I'm not a Windows user and I don't develop any projects on Windows, so I don't speak for that. From what you're saying, it seems that dog-fooding and Windows are the only two things Az DevOps is good for.
Chastina, I agree with Luciano. We use Azure DevOps to deploy Java artifacts from AWS S3 to Amazon Linux EC2 instances because it has better release functionality than AWS Code Pipeline. I would agree with Luciano that you don't have a good grasp of the features.
Maybe I spoke too soon. No I haven't used AWS Code Pipeline or used Azure DevOps the way you used it. I'm speaking for my personal experience with it and so far it sucked. I built better CICD solutions myself on bare Jenkins. I apologize if what I said offended any of the Azure DevOps users out there that had pleasant experiences with it. I'm just speaking for my experience and I don't need to have to have used all of the CICD products out there to be able to then say what I felt.
Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
"The last paragraph of your article makes clear you have no idea about what you're saying.". If you'd be gracious enough, it would be helpful if you could point out a better way to do what Chastina is doing. DEV encourages individuals to share their experiences, and that means sharing when we're new to a given technology, and we might not have an expert understanding.
Personally, I have 0 experience with Azure DevOps so I can't really comment, but it seems like you're insinuating there's some way to avoid manually installing dependencies in the build steps when using modules? If possible, let us know the better way! :)
MS Team Services/Visual Studio Online was a popular product inside MS dev community... but nobody knew it outside that niche (yes, it is a niche, nothing wrong about that).
Once it has been rebranded to Azure DevOps (and divided into meaningful separated components) its popularity has raised over the radar of a much broader audience. But you cannot compare the documentation available for it with the resources associated with products like Jenkins.
It is a very nice managed alternative, and I'm sure it is going to be very popular once it becomes possible to define release pipelines with code (not only build pipelines) and more plugins become available.
That said, discouraging new users that are actually creating good resources for Azure DevOps community using rudeness is really against the best interest of the company you clearly love and the team behind Azure DevOps.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, the last paragraph of your article makes clear you have no idea about what you're saying.
Az DevOps is used by all engineering teams in Microsoft, just to mention the Windows Universal Platform (Windows, Xbox Live and other products) dev team has ~22k developers with ~500Gb of source code, so to support this size of project, Microsoft created a Virtual Filesystem for Git (github.com/Microsoft/VFSForGit/blo...).
Despite this one, there are tons of other use cases, even the Az DevOps team which generates thousands of the builds daily as well as office team which generates 7Tb of pdb files stored in Az DevOps for production debuging purposes.
Sorry but if you don't know how to use Az DevOps, it is not a problem of the product, but yours.
Sincerely, Luciano.
I don't care if Microsoft is dog-fooding their own product, as an outsider and someone who's used and built similar products, Azure DevOps has given me a bad user experience. It does't matter if the employees are using the product (they probably don't have choice anyway), at the end of the day they have to sell it and I definitely won't buy it. And I'm not a Windows user and I don't develop any projects on Windows, so I don't speak for that. From what you're saying, it seems that dog-fooding and Windows are the only two things Az DevOps is good for.
Chastina, I agree with Luciano. We use Azure DevOps to deploy Java artifacts from AWS S3 to Amazon Linux EC2 instances because it has better release functionality than AWS Code Pipeline. I would agree with Luciano that you don't have a good grasp of the features.
Maybe I spoke too soon. No I haven't used AWS Code Pipeline or used Azure DevOps the way you used it. I'm speaking for my personal experience with it and so far it sucked. I built better CICD solutions myself on bare Jenkins. I apologize if what I said offended any of the Azure DevOps users out there that had pleasant experiences with it. I'm just speaking for my experience and I don't need to have to have used all of the CICD products out there to be able to then say what I felt.
"The last paragraph of your article makes clear you have no idea about what you're saying.". If you'd be gracious enough, it would be helpful if you could point out a better way to do what Chastina is doing. DEV encourages individuals to share their experiences, and that means sharing when we're new to a given technology, and we might not have an expert understanding.
Personally, I have 0 experience with Azure DevOps so I can't really comment, but it seems like you're insinuating there's some way to avoid manually installing dependencies in the build steps when using modules? If possible, let us know the better way! :)
MS Team Services/Visual Studio Online was a popular product inside MS dev community... but nobody knew it outside that niche (yes, it is a niche, nothing wrong about that).
Once it has been rebranded to Azure DevOps (and divided into meaningful separated components) its popularity has raised over the radar of a much broader audience. But you cannot compare the documentation available for it with the resources associated with products like Jenkins.
It is a very nice managed alternative, and I'm sure it is going to be very popular once it becomes possible to define release pipelines with code (not only build pipelines) and more plugins become available.
That said, discouraging new users that are actually creating good resources for Azure DevOps community using rudeness is really against the best interest of the company you clearly love and the team behind Azure DevOps.