Description de Azure DevOps Services
Package DevOps qui simplifie le développement de logiciels via le contrôle de code source et de packages, les tests et l'automatisation du déploiement des applications.
Qui utilise Azure DevOps Services ?
Non fourni par l'éditeur
Azure DevOps Services ne vous convainc pas tout à fait ?
Comparer avec une alternative populaire
Azure DevOps Services
Alternatives à Azure DevOps Services
Avis sur Azure DevOps Services
facile d'utilisation, elle permet de gérer tout le processus devops d'un logiciel quel que soit l'échelle de déploiement de celui ci
le service client peut etre lent à réagir
Alternatives envisagées précédemment :
A fantastic offering for small development teams
Commentaires : We've improved a number of key workflows with Azure DevOps and it's proved to be an invaluable addition to our software development cycle.
The service provides a lot under the one package, task management, source control, CI/CD, and release pipelines. If you are a small team or just starting off, you'll be able to take advantage of it all for either free, or very little money. It's clearly designed to get teams hooked on Azure and it does this job well.
The UI is clunky in places, task management specifically leaves a lot to be desired. While the close integration with source control is fantastic, editing and navigating between tasks take far too long and you're much more likely to avoid doing it or take a lot longer to complete a simple job.
Alternatives envisagées précédemment :
Tools for doubling productivity
Commentaires : Many plugins and events, such as git repository updates, can be triggered to run builds and tests automatically. By continuously building and testing, it is possible to detect deviations and defects early and improve the quality and efficiency of development.
The functionality can be extended with add-ons; since there are many add-ons, you can do a wide range of things. Being able to do certain things even when engineers are not present also helps to keep the product running stably.
I would be happy if the manual to consult when I don't understand the operation is a little more complete.
A basic functional Review
Overall experience is neutral.
Looking forward if they improve the product.
The software has many advantages - 1. Complete bundle/package to push a build on production. 2.Can keep all the builds/production code with versioning. 3.Bug, User story, accès rights are very well segregated. 4. From assigning a new user story to making a task and assigning bug the process is complete, you do not need any other software to manage the team. 5.Can be easily integrated with GitHub too(if you have paid version of both) 6.Security wise a good and trustable product.
There are some cons too which I felt- 1. Firstly the azure dashboard takes too long to load/ refresh (without any wifi/internet issue). 2. Many times it just stuck on a single page. 3. As they are providing a complete package of multiple functionality , the smooth user interface is missing. Literally many times you just have to search for a single things and you will be puzzled in the complete dashboard. 4.If you have a lot of number of projects ongoing and you are part of a big project with multiple members, the user story is not very clear. 5. Options of "not replicable" and many options are missing in bug lifecycle. They should add more lifecycle to task and bugs for better clarity.
Microsoft's one stop shop for planning, task, code, versions and releases management
Commentaires : If I get a say in the selection of tooling before starting the project, Azure DevOps is my go to.
It's a full suite usable directly as is with very little configuration needed to get a jump start. Customizations and integrations are still possible though. I like the work experience better with Azure DevOps board rather than one of the competing backlog/task management suites.
The Azure DevOps Boards seems a bit forgotten/sunsetting tool but hopefully there would be still future new features and enhancements to make it even better.Git approvals workflow really should be much more seamless so that either work from developer and approver perspective is only done in Git and automatically reflects to Azure DevOps tasks/work items. Or other way around, approval requests would get populated as task on board and moving it to done column would automatically approve pull request in Git. There is some still unlocked potential there with integration and seamless working experience.