Azure DevOps

What differentiates Azure DevOps from other similar products?

It is intended to work with Visual Studio, however, because the source code at check-in time may be stored on the cloud, it is useful for tracking older code. It is also necessary to be able to assess where the most recent local source has changed in reference to the source at final check-in time. Comparing the source being revised to the source you last recorded can help you determine where you need to publish later since you can see what has changed.

What is your favorite aspect of this product?

For those new to agile development, not just the CI/CD function, but also the ability to create a Kanban board, is accessible. Integrating with Teams and Visual Studio is a breeze. It was quite easy to generate YAML by entering in the GUI when establishing processes. Because the code history may be kept in the cloud, you are significantly less likely to comment out bits of code that are no longer required. It assists in the location of the source.

What do you dislike most about this product?

It is not ideal for waterfall development because there is no Gantt chart as in MS Project. If this issue is resolved, I believe it will be widely adopted by businesses.

What recommendations would you give to someone considering this product?

If you're a developer who doesn't have authority over the source, it's free, so I think you should give it a shot for the time being. However, there are certain oddities in the movement that might be difficult to adjust to. Normally, I have a development environment as the internal checkout environment and a production environment as the client environment, however transitioning between the two was a breeze. You may ship and deploy directly, using the access token to connect to external repositories and the primary service mechanism.

What differentiates Azure DevOps from other similar products?

A comprehensive Git repository and project management application that is available for free. There are no restrictions on the number of persons, capacity, or projects that may be formed, and you can freely set up as many repositories as you wish for each one. Although GitHub appears to have a policy of committing and preserving all files associated with a repository, DevOps may easily adopt a policy of managing relevant tools and documentation in another repository. This allows testing and deployment to be reliable in a remote location, which makes it much less than before. It's easy to use, so I think it's a great place to start.

What is your favorite aspect of this product?

Git supports an almost endless number of repositories. There is no need for you to be concerned about the size of the files or the repository. The idea is that you can use it as often as you like, leading the local repository to grow bloated and ridiculous. In addition, CI and Kanban technologies are available, and installation may be done in collaboration with other services. I had little experience with CI and automation, which made it tough to work with other services, but with DevOps, when I decided on the wizard format, it quickly constructed a YAML definition file, and an implementation plan was easily established.

What do you dislike most about this product?

Following Microsoft's acquisition of GitHub, it is unclear whether DevOps or GitHub will continue to exist. If it ever goes away, I believe it will be DevOps. On the other hand, the development team is working hard to get release information up on the site.

What recommendations would you give to someone considering this product?

It is now possible to manage multiple repositories project by project and commit and push without regard for capacity or payment. Users from other companies can now be easily invited. We clarified the internal policy by separating the tools and repositories on the network that are open to the public to use GitHub since GitHub has some elements that are difficult to pull into GitHub. The hiding policy is simple to comprehend on the DevOps side, making it easier to execute.

What differentiates Azure DevOps from other similar products?

It is highly customisable and world wide accepted language and there are many features that make Devops superior

What is your favorite aspect of this product?

I like how easy and interactive it is to develop software and application using this software

What do you dislike most about this product?

Sometimes debugging task take much time and there is no shortcut in there

What recommendations would you give to someone considering this product?

This product is versatile and accepted bi many clients so this will stay here for long time in it is very easy to learn