Automated Release Pipelines with Azure DevOps
Download as PPTX, PDF1 like349 views
The document outlines the principles and practices of DevOps, particularly in the context of ASP.NET Core and Entity Framework Core applications. It emphasizes the importance of automation, version control, and frequent releases to enhance productivity and reduce errors in software deployment. Additionally, it provides a checklist for implementing DevOps practices, including managing database changes and utilizing Azure DevOps pipelines.
Automated Release Pipelines with Azure DevOps
- 1. @benday | www.benday.com Continuous Deployment to Azure with Azure DevOps Pipelines Benjamin Day | www.benday.com | @benday
- 2. @benday | www.benday.com Benjamin Day Brookline, MA Consultant & Trainer Scrum, DevOps, Team Foundation Server, Software Architecture & Testing Microsoft MVP Pluralsight Author Scrum.org Trainer @benday
- 3. Architecting an ASP.NET Core MVC Application for Unit Testability January 1, 2019
- 4. Getting Started with Azure DevOps Coming soon
- 5. On with the show.
- 6. Busy?
- 7. @benday | www.benday.com Too busy?: Productivity vs. Waste "Quality Software Management: Vol. 1 System Thinking“, Gerald Weinberg (1992) 100% 40% 20% 10% 5% 40% 20% 10% 5% 20% 10% 5% 10% 5% 5% 20% 40% 60% 75% 1 TASK 2 TASKS 3 TASKS 4 TASKS 5 TASKS Task A Task B Task C Task D Task E Waste
- 8. Humans are terrible at multitasking.
- 9. To be productive, eliminate distractions.
- 10. Software delivery not software development.
- 11. Anything that slows you down, automate it.
- 13. What is DevOps?
- 14. DevOps is a mindset plus a set of practices that focuses on automation.
- 15. Why DevOps? Minimize distractions. Make delivery & deployment easy.
- 16. Hint: You want more frequent releases.
- 17. @benday | www.benday.com If delivery & deployment is easy… …it’s not a big deal to do a release - (Hopefully, without much human involvement) …you’ll do releases more often …you can focus more time writing & delivering features
- 18. Smaller, more frequent releases smaller batch size
- 19. @benday | www.benday.com Semi-Annual Releases Large Batch Size Daily / Weekly Releases Small Batch Size
- 20. Smaller, more frequent releases are easier to manage & less to worry about.
- 22. @benday | www.benday.com DevOps for ASP.NET Core & EF Core
- 23. @benday | www.benday.com DevOps Goals Version Controlled, Automated, Repeatable - Ideally, including hosting environment configuration - (Docker, ARM templates, etc) Never deploy from a developer workstation - No right-click deploy Deploy from TFS Build Deploy from TFS Release Management Pipeline
- 24. @benday | www.benday.com ASP.NET Core & EF Core DevOps Checklist Code is under version control Database schema & changes are under version control Automated tests (unit tests, integration tests, UI tests) Automated build Automated release / deployment
- 25. @benday | www.benday.com DevOps: Don’t Forget the Database! Does your app use a database? - You’ll need to version control it Automated build & deploy of database schemas Two approaches: - SQL Server Data Tools (SSDT) - Entity Framework Migrations
- 26. DevOps Tip: Learn how to do everything from the command line
- 27. @benday | www.benday.com Demo: Manage Your Database Changes with EF Core Migrations
- 28. EF Core & EF Core Migrations Summary
- 29. @benday | www.benday.com EF Core NuGet Packages Talk to SQL Server Microsoft.EntityFrameworkCore.SqlServer Database Updates (“Migrations”) Microsoft.EntityFrameworkCore.Design Reverse Engineer a SQL Server Database Microsoft.EntityFrameworkCore.SqlServer.Design
- 30. @benday | www.benday.com Enable the “dotnet ef” Command Edit *.csproj Add DotNetCliToolReference to Microsoft.EntityFrameworkCore.Tools.DotNet
- 31. EF Migrations = Entity Framework Version Control
- 32. @benday | www.benday.com Migrations from the Command Line Add / Remove a Migration dotnet ef migrations add “{name}” dotnet ef migrations remove Deploy an Update dotnet ef database update
- 33. @benday | www.benday.com Things you need for EF Core Entity Framework DB Context - Starting point for all your database operations - Microsoft.EntityFrameworkCore.DbContext IDesignTimeDbContextFactory<T> - Handles creating instances of DbContext for doing migrations - Microsoft.EntityFrameworkCore.Design.IDesignTimeDbContextFactory
- 34. Hosting ASP.NET Core on IIS
- 35. @benday | www.benday.com Host ASP.NET Core on IIS Install .NET Core Windows Server Hosting Bundle - ASP.NET Core 1.* https://go.microsoft.com/fwlink/?linkid=848766 - ASP.NET Core 2.* https://aka.ms/dotnetcore.2.0.0-windowshosting
- 36. Azure DevOps Builds & Releases Azure DevOps Pipelines
- 37. @benday | www.benday.com Demo: Azure DevOps Build
- 38. Monumental Gotcha: “dotnet ef database update” assumes that you have the source code…
- 39. (…and you won’t have your source code when you do a release.)
- 40. @benday | www.benday.com Demo: Azure DevOps Release
- 41. @benday | www.benday.com ASP.NET Core & EF Core DevOps Checklist Code is under version control Database schema & changes are under version control Automated tests (unit tests, integration tests, UI tests) Automated build Automated release / deployment