What is Azure DevOps?
Who uses Azure DevOps?
Azure DevOps Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Azure DevOps in their tech stack.
Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps
#Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.
Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.
Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure
I use Azure DevOps because for me it gradually walk me from private Git repositories to simplest free option for CI/CD pipelines at the time. I spend 0$ initially to manager CI/CD for my small private projects. No need to go into two different places to setup integration, once I have git repository, I could deploy projects. Right now this is not the case since CI/CD is default for me, so I use it now from memories of old good days. I'm not yet need complexity on the projects, so I don't even consider other options with "more choices". I carefully limit my set of options during development, that's why Azure DevOps (VSTS)
Secure Membership Web API backed by SQL Server. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD.
We have .Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. For this service I opted to keep it as a classic WebAPI project and deployed to AppService.
- Trusted Authentication Provider: @AzureActiveDirectoryB2C
- Frameworks: .NET Core
- Language: C# , Microsoft SQL Server , JavaScript
- IDEs: Visual Studio Code , Visual Studio
- Libraries: jQuery @EntityFramework, @AutoMapper, @FeatureToggle , @Swashbuckle
- Database: @SqlAzure
- Source Control: Git
- Build and Release Pipelines: Azure DevOps
- Test tools: Postman , Newman
- Test framework: @nUnit, @moq
- Infrastructure: @AzureAppService, @AzureAPIManagement
VSO/Team Services are a natural extension of my TFS experience. Manage projects, version control, testing & continuous integration pipeline (CI/CD). Integration with Azure. Full SDLC. Visual Studio Team Services
Code version and integration with QA and develop teams Visual Studio Team Services
We use VSTS to host our repos, to manage our backlog and plan our sprints, to track our work (tasks and bugs), host our knowledge-base (wiki) and a lot more. I am the team admin. Visual Studio Team Services
Azure DevOps's Features
- Agile Tools: kanban boards, backlogs, scrum boards
- Reporting: dashboards, widgets, Power BI
- Git: free private repositories, pull requests
- Continuous Integration: automated builds and diagnostics
- Cloud build agents: cross-platform agents for Windows, Mac and Linux
- Testing Tools: unit testing, load testing, manual, exploratory and user acceptance testing
- Release Management: automate deployments, gated approval workflows, audit trails
- Marketplace: extensions for the Visual Studio family of products
- Package Management: host npm and NuGet packages
- IDE Support: Eclipse, IntelliJ, Xcode and Visual Studio
- Integration: link code and releases to work items, builds, and test results
