Skip to content

Commit cdfdde7

Browse files
committed
Updated section F and image
1 parent 156726b commit cdfdde7

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -459,7 +459,7 @@ In this step, we will deploy an instance of Azure Container Registry to store co
459459
### F] Define and execute Claims API Build pipeline in Azure DevOps
460460
**Approx. time to complete this section: 1 Hour**
461461

462-
In this step, we will create a **Continuous Integration** (CI) pipeline in Azure DevOps. This pipeline will contain the tasks for building the microservice (binary artifacts) and packaging (layering) it within a docker container. During the application container build process, the application binary is layered on top of a base docker image (mcr.microsoft.com/dotnet/core/aspnet). Finally, the built application container is pushed into ACR an which you deployed in Section [E].
462+
In this step, we will create a **Continuous Integration** (CI) pipeline in Azure DevOps. This pipeline will contain the tasks for building the microservice (binary artifacts) and packaging (layering) it within a docker container. During the application container build process, the application binary is layered on top of a base docker image (mcr.microsoft.com/dotnet/core/aspnet). Finally, the application container image is pushed into the ACR which you deployed in Section [E].
463463

464464
Before proceeding with the next steps, take a few minutes and go thru the **dockerfile** and Claims API source files in the GitHub repository. This will help you understand how the container is built when the continuous integration (CI) pipeline is executed in Azure DevOps Services.
465465

@@ -495,7 +495,7 @@ Before proceeding with the next steps, take a few minutes and go thru the **dock
495495
496496
![alt tag](./images/F-05.PNG)
497497
498-
In the *New pipeline* definition wizard, click on **Use the classic editor** as shown in the screenshot below. We will use the *YAML Delivery Pipeline** feature in a subsequent lab.
498+
In the *New pipeline* definition wizard, click on **Use the classic editor** as shown in the screenshot below. We will use the **YAML Delivery Pipeline** feature in a subsequent lab.
499499
500500
![alt tag](./images/F-23.PNG)
501501

images/F-20.PNG

55.6 KB
Loading

0 commit comments

Comments
 (0)