From eb4d2db622be3f900a53fd60170de902487114c0 Mon Sep 17 00:00:00 2001 From: preethi doss Date: Tue, 1 Jun 2021 20:20:02 +0530 Subject: [PATCH 1/3] Lab 19, added changes to Instructions in Exercise 1 Task 2, fix for Maven build. --- ...y_and_Compliance_in_an_Azure_DevOps_pipeline.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md index 43c161b6c..a8c0e9767 100644 --- a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md +++ b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md @@ -92,11 +92,19 @@ In this task, you will activate WhiteSource Bolt in the newly generated Azure De In this task, you will trigger a build within your Java code-based Azure DevOps project. You will use **WhiteSource Bolt** extension to identify vulnerable components present in this code. -1. On your lab computer, in the web browser window displaying the Azure DevOps portal with the **WhiteSource Bolt** project open, in the vertical menu bar on the left side, in the **Pipelines** section, click **Pipelines**. -1. On the **Pipelines** pane, select the **WhiteSourceBolt** build definition, click **Run pipeline** and, on the **Run pipeline** pane, click **Run** to trigger a build. +1. On your lab computer, in the web browser window displaying the Azure DevOps portal with the **WhiteSource Bolt** project open, in the vertical menu bar on the left side, click **Repos** and navigate to **WebGoat**. + + > **Note**: As the project uses Maven to compile the project files, latest Maven release of 3.8.1 blocks HTTP artifactories. To successfully build the project, you will have to change pom.xml file in the Project to use HTTPS instead of HTTP under PluginRepositories section. Perform below step for this purpose. + +1. Inside **webgoat-container** project files and Identify pom.xml file and click on **Edit** on the top right corner. Search for the section **pluginRepositories** inside the pom.xml file. Change the url http://repository.apache.org/snapshots/ to https://repository.apache.org/snapshots/ + +1. As the **Commit** button is enabled after your edit, click on **Commit** + +1. On the Vertical bar, navigate to **Pipelines** section and click **Pipelines** pane, observe build is automatically triggered due to previous commit of pom.xml file. + 1. On the build pane, on the **Summary** tab, in the **Jobs** section, click **Phase 1** and monitor the progress of the build process. - > **Note**: The build definition consists of the following tasks: + > **Note**: The build may take a few minutes to complete. The build definition consists of the following tasks: | Tasks | Usage | | ---- | ------ | From c955de8115cb2650428e2e365d0f48a322dee202 Mon Sep 17 00:00:00 2001 From: preethi doss Date: Tue, 15 Jun 2021 15:17:42 +0530 Subject: [PATCH 2/3] Changes to sentence correction --- ...Security_and_Compliance_in_an_Azure_DevOps_pipeline.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md index a8c0e9767..31b9c0044 100644 --- a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md +++ b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md @@ -94,13 +94,13 @@ In this task, you will trigger a build within your Java code-based Azure DevOps 1. On your lab computer, in the web browser window displaying the Azure DevOps portal with the **WhiteSource Bolt** project open, in the vertical menu bar on the left side, click **Repos** and navigate to **WebGoat**. - > **Note**: As the project uses Maven to compile the project files, latest Maven release of 3.8.1 blocks HTTP artifactories. To successfully build the project, you will have to change pom.xml file in the Project to use HTTPS instead of HTTP under PluginRepositories section. Perform below step for this purpose. + > **Note**: As the project uses Maven to compile the project files, latest Maven release of 3.8.1 blocks HTTP artifactories. To successfully build the project, you will have to change the pom.xml file of the Project, to use HTTPS instead of HTTP. Perform below step for this purpose. -1. Inside **webgoat-container** project files and Identify pom.xml file and click on **Edit** on the top right corner. Search for the section **pluginRepositories** inside the pom.xml file. Change the url http://repository.apache.org/snapshots/ to https://repository.apache.org/snapshots/ +1. Inside **webgoat-container** project file, identify the pom.xml file and click on **Edit** on the top right corner. Search for the section **pluginRepositories** inside the pom.xml file. Change the URL http://repository.apache.org/snapshots/ to https://repository.apache.org/snapshots/ -1. As the **Commit** button is enabled after your edit, click on **Commit** +1. Once the **Commit** button is enabled after your edits, click on **Commit**. -1. On the Vertical bar, navigate to **Pipelines** section and click **Pipelines** pane, observe build is automatically triggered due to previous commit of pom.xml file. +1. In the vertical menu bar on the left side, navigate to **Pipelines** section and click **Pipelines**. Observe the build, while it has automatically triggered due to the commit action performed in the previous step. 1. On the build pane, on the **Summary** tab, in the **Jobs** section, click **Phase 1** and monitor the progress of the build process. From a541e0f2fb5788180a08a3846a3a9572ea868637 Mon Sep 17 00:00:00 2001 From: preethi doss Date: Thu, 24 Jun 2021 21:07:29 +0530 Subject: [PATCH 3/3] Fixing additional sentence corrections for PR #84 --- ...t_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md index 31b9c0044..75a48a3af 100644 --- a/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md +++ b/Instructions/Labs/AZ400_M19_Implement_Security_and_Compliance_in_an_Azure_DevOps_pipeline.md @@ -94,13 +94,13 @@ In this task, you will trigger a build within your Java code-based Azure DevOps 1. On your lab computer, in the web browser window displaying the Azure DevOps portal with the **WhiteSource Bolt** project open, in the vertical menu bar on the left side, click **Repos** and navigate to **WebGoat**. - > **Note**: As the project uses Maven to compile the project files, latest Maven release of 3.8.1 blocks HTTP artifactories. To successfully build the project, you will have to change the pom.xml file of the Project, to use HTTPS instead of HTTP. Perform below step for this purpose. + > **Note**: As the project uses Maven to compile the project files, the latest Maven release of 3.8.1 blocks HTTP artifactories. To successfully build the project, you will have to change the pom.xml file of the project, to use HTTPS instead of HTTP. Perform below steps for this purpose. -1. Inside **webgoat-container** project file, identify the pom.xml file and click on **Edit** on the top right corner. Search for the section **pluginRepositories** inside the pom.xml file. Change the URL http://repository.apache.org/snapshots/ to https://repository.apache.org/snapshots/ +1. Inside the **webgoat-container** project file, identify the pom.xml file and click on **Edit** on the top right corner. Search for the section **pluginRepositories** inside the pom.xml file. Change the URL http://repository.apache.org/snapshots/ to https://repository.apache.org/snapshots/ 1. Once the **Commit** button is enabled after your edits, click on **Commit**. -1. In the vertical menu bar on the left side, navigate to **Pipelines** section and click **Pipelines**. Observe the build, while it has automatically triggered due to the commit action performed in the previous step. +1. In the vertical menu bar on the left side, navigate to the **Pipelines** section and click **Pipelines**. Observe the build, while it has been automatically triggered by the commit performed in the previous step. 1. On the build pane, on the **Summary** tab, in the **Jobs** section, click **Phase 1** and monitor the progress of the build process.