1
0
Форкнуть 0
MCW Continuous delivery in Azure DevOps
Перейти к файлу
Dawnmarie DesJardins 8fd5e9bd1d
Update README.md
Archiving workshop
2022-07-29 13:58:36 -07:00
.github/ISSUE_TEMPLATE Initial submission 2021-06-28 10:44:05 -05:00
Hands-on lab Adding commands for Exercise 1, Task 1, Step 5 #126 2022-04-13 11:55:32 -04:00
Whiteboard design session Markdownlint fixes 2021-11-05 12:38:06 -04:00
.gitignore updated Exercise 2 2019-01-17 13:33:22 -05:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2021-04-20 15:37:04 -07:00
CONTRIBUTING.md refactor into folders 2018-06-07 06:19:33 -05:00
HTMLLINKS.md Updated HTML links. 2021-07-22 11:43:54 -07:00
LICENSE updated license to MIT 2018-06-08 05:51:39 -05:00
README.md Update README.md 2022-07-29 13:58:36 -07:00
SECURITY.md Create SECURITY.md 2021-04-20 15:36:38 -07:00

README.md

Continuous delivery in Azure DevOps

This workshop is archived and no longer being maintained. Content is read-only.

Fabrikam Medical Conferences provides conference web site services tailored to the medical community. They started out 10 years ago building a few conference sites for a small conference organizer. Since then, word of mouth has spread, and Fabrikam MedicalConferences is now a well-known industry brand. They currently handle over 100 conferences per year and growing.

Websites for medical conferences are typically low budget web sites because the conferences usually have between 100 to 1500 attendees. At the same time, the conference owners have significant customization and change demands that require turnaround on a dime to the live sites. These changes can impact various aspects of the system from UI through to the back end, including conference registration and payment terms.

The VP of Engineering at Fabrikam, Susan Withers, has a team of 12 developers who handle all aspects of development, testing, deployment, and operational management of their customer sites. Due to customer demands, they have issues with the efficiency and reliability the conference websites. This mainly caused by an inefficient development and operations workflow.

November 2021

Target audience

  • Application Developer

Abstracts

Workshop

In this workshop, you will learn how to setup and configure continuous delivery within Azure and GitHub. You will do this through the use of a new Azure DevOps project, GitHub repository for source control, GitHub actions for continuous delivery and deployment automation, and an Azure Resource Manager (ARM) template for Azure resource deployment and configuration management.

At the end of this workshop, you will be able to build templates to automate cloud infrastructure and reduce error-prone manual processes. In addition, you'll create an ARM template to provision Azure resources, configure continuous delivery with Azure DevOps, and create an Azure DevOps project and Git repository.

Whiteboard design session

In this whiteboard design session, you will learn how to design a solution with a combination of ARM templates, Azure DevOps, and GitHub actions to enable continuous delivery with several Azure PaaS services.

At the end of this workshop, you will be better able to build templates to automate cloud infrastructure and reduce error-prone manual processes. In addition, you'll learn how to design a deployment and monitoring architecture using ARM templates to provision Azure resources, Application Insights for deep application monitoring, and GitHub as a source code repository and build/deploy pipeline.

Hands-on lab

In this hands-on lab, you will learn how to implement a solution with a combination of ARM templates and Azure DevOps to enable continuous delivery with several Azure PaaS services.

At the end of this workshop, you will be better able to implement solutions for continuous delivery with GitHub in Azure, as well create an ARM template to provision Azure resources, create an Azure DevOps project with a GitHub repository, and configure continuous delivery with GitHub.

  • Azure App Service
  • Azure Cosmos DB API for MongoDB
  • Application Insights
  • Azure Resource Manager
  • Azure DevOps

Help & Support

We welcome feedback and comments from Microsoft SMEs & learning partners who deliver MCWs.

Having trouble?

  • First, verify you have followed all written lab instructions (including the Before the Hands-on lab document).
  • Next, submit an issue with a detailed description of the problem.
  • Do not submit pull requests. Our content authors will make all changes and submit pull requests for approval.

If you are planning to present a workshop, review and test the materials early! We recommend at least two weeks prior.

Please allow 5 - 10 business days for review and resolution of issues.