VSTS DevOps

Kommentare: Dev Ops (VSTS or TFS) has been the main place I store my code through version control and plan out projects for my current and previous job. Either way of version control you use for your code (TFVC or Git) has a great integration with Visual Studio. From there you can check in or push your changes and once it's hooked up to Dev Ops, it'll appear in the Repos section. You can set the code to build and run all tests by setting a new build in the Pipeline section, along with setting up builds for releases. These have helped immensely when dealing with the program working on other computers. The main issue I've had with Dev Ops is finding some settings. There has been a few times where it took diving into a few different spots just to figure out how to customize a field. It's also easy to get lost when you're still learning, as there is so much out there.

Vorteile: There is a ton of features.
They just did a new design and rebranded it.
You can set automatic builds to test your code.
It allows for organized planning through the Boards section.
There is easy integration with Azure Cloud.
It allows use of either Git or TFVC.

Nachteile: With all of the features, it's easy to get lost.
Settings and security seems to be all over the place, so it's hard to track down the setting you need.
There's a learning curve if you haven't used VSTS or TFS before.

Kommentare: Microsoft VSTS DevOps is the best move by the Microsoft, as DevOps is the advanced software development strategy. Continuous Testing with integration of xUnit, jUnit and Selenium make it more flexible. Automation build & Deploy with vNext is good as compared to XML build. Collection code coverage is also good. The Azure DevOps enables DevOps for all platform's software development.

Vorteile: Microsoft Visual Studio Team Service DevOps is also known as VSTS DevOps. Development in DevOPS methodology is way fast then the agile. It accelerates the development process and developer. Build & Release is also enhance from the previous version and easy to manage the complex merges while release of the different product. Continuous delivery of the product also help the developer to work and focus on the single task which help in increasing the productivity. Automation Test and Monitoring of application possible with it.

Nachteile: TFSVC work-space are complex and managing the permission for security is mess up if we select some inappropriate setting. Resolving and fixing it is a big challenge., Microsoft should come with the backup or restore point for the same so if it can be easy to fix can and restore on the earlier position.

Kommentare: Since our company has started using VSTS, I found it very helpful and it has made our work so much easier. We can now all work on the same project at the same time, we have our pipelines and builds going well, so deployments are no longer such a huge concern in terms of reliability and roll-back capability. There is much that I still have to learn, but from what I have experienced so far, I will not use any other version control system.

Vorteile: Having recently started working with VSTS, I found it capable of so much in terms of version control, continuous integration and also project management(Yes Project Management). The idea of having everything you need in one place, has always been a challenge in many teams. With VSTS DevOps, everyone knows what is happening, from management, to developers, to project managers.
You can see exactly what was changed, by whom and when.
Project managers can plan and allocate tasks to developers and track their progress.
Other than the version control and tracking of progress, continuous integration and delivery enables a seamless link from dev to staging to production and everything in between.
VSTS is indeed a powerful tool that not many can compete with.

Nachteile: I find it a bit difficult to navigate through. Due to the large scope of functionality, I find myself with too much info at times. From your menu to the left, it branches out to so many different pages.

Kommentare: I thinks its a very robust tool which, being integrated into Visual Studio, makes it great especially for devs. From my product manager viewpoint, I like that its easy to track versions and work items, making my work easier and ensuring I dont loose track of anything.

Vorteile: I think the best about VSTS is the ability to be able to comment on work items, naming people, so that they are notified of what comments you make. This makes it very agile to cooperate and collaborate with my team. Everyone knows what to do, there is traceability, and, for the first time, all the info we need to work is in a single place. Linking and ordering work items by hierarchy is also a great feature that I really like.

Nachteile: Its a bit hard to get used. There are a few features we are not even using because we do not full understand them. Kanban boards are not that intuitive and we end up using old lists usually. I also find it annoying that I cannot order by columns when looking at a sprint or backlog, I can only do that in queries.

Kommentare: VSTS DevOps is helping use to manage team ,code and operation. We are using it with Azure Cloud and the experience is really good. vNext build is able to build the .net Core application easily.

Vorteile: VSTS DevOps provide the complete integrity with Development and Operational work. The architecture is helping in boosting the development & Operational process. VSTS take care for complete CI/CD pipeline. Best and loving part in it is that it provide freedom in selecting the TFVC or GIT as version controlling.
Integrity with Azure Cloud is also good which it make this tool a complete DevOps system so that it can be achieve the deployment part with zero outage. XAML and vNext build help in deployment of 100's servers without any human error, as it just need one time setup for builds.

Nachteile: Installation architecture of VSTS DevOps having a lot of curves, Build Controller and Gated Build need time to setup and Microsoft should make it easy to under and setup. In last few years I am seeing the changes the it moving towards the web-based application, Console like security and permission are now only available in web base pages only.