Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Updates to GitHub integration lab with new sections #12

Merged
merged 5 commits into from
Jul 11, 2019
Merged

Updates to GitHub integration lab with new sections #12

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
78c8cd4
updates to a section of the lab
Hoyg Jul 9, 2019
22a79c3
Merge branch 'gh-pages' of https://github.com/microsoft/TailwindTrade…
Hoyg Jul 9, 2019
a3ebe62
Updated new exercises and screenshots
Hoyg Jul 9, 2019
8a03c7a
updated some steps
Hoyg Jul 9, 2019
f550123
updated lab and screenshots
Hoyg Jul 10, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
updated some steps
  • Loading branch information
@Hoyg
Hoyg committed Jul 9, 2019
commit 8a03c7aa094a1a4e16a9adb17abb8329779b925d
20 changes: 8 additions & 12 deletions ...ents/DemoScripts/Integrating Azure Pipelines, GitHub and Azure Boards/Readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ In this demo, we'll be illustrating the integration and automation benefits of A

Now that Azure Pipelines has been installed and configured, we can start building the pipelines but we will need to select a project where the pipeline will be saved. You may select an existing or create a new Azure DevOps project to hold and run the pipelines we need for continuous integration and continuous delivery. The first thing we'll do is to create a CI pipeline.

1. Select the organization and Azure DevOps project that you created using the Azure DevOps Demo Generator. Click **Create a new pipeline** under Builds. Choose **GitHub(YAML)** as the code repository and follow the next steps to select the forked repository in your GitHub account.
1. Select the organization and Azure DevOps project that you created using the Azure DevOps Demo Generator. Click **Create a new pipeline** under Builds. Choose **GitHub(YAML)** as the code repository and follow the next steps for authorization.

![Choose code repo](Images/coderepo.png)

Expand All @@ -70,7 +70,7 @@ Now that Azure Pipelines has been installed and configured, we can start buildin

![Starter_pipeline](Images/Starter_pipeline.png)

1. Replace the default template with the below YAML snippet.
1. Replace the default template with the below YAML snippet and substitute variables section with relevant values below.

```yaml
variables:
Expand Down Expand Up @@ -127,7 +127,7 @@ Now that Azure Pipelines has been installed and configured, we can start buildin

![job-summary](Images/job_summary.png)

## Task 3: Adding a build status badge
### Adding a build status badge

An important sign for a quality project is its build status badge. When someone finds a project that has a badge indicating that the project is currently in a successful build state, it's a sign that the project is maintained effectively.

Expand Down Expand Up @@ -180,21 +180,17 @@ An important sign for a quality project is its build status badge. When someone

![badge_status](Images/badge_status.png)

## Task 4: Configuring the Azure Continuous Delivery Pipeline
### Configuring the Azure Continuous Delivery Pipeline

Now that the build pipeline is completed we can turn our attention to creating a release pipeline.

Like the build templates, there are many packaged options available that cover common deployment scenarios, such as publishing to Azure. But to illustrate how flexible and productive the experience is, we will build this pipeline from an empty template.

1. Select **Releases**.
1. Select **Releases**. You will see 2 release pipelines already created by the Demo Generator. But, let's go ahead and define our own pipeline.

![releases](Images/releases.png)

1. Click **New pipeline**.

![new-pipeline](Images/new-pipeline.png)

1. Click **Empty job**.
1. Click **New pipeline** and click **Empty job**.

![select-template](Images/select-template.png)

Expand Down Expand Up @@ -253,11 +249,11 @@ Like the build templates, there are many packaged options available that cover c

![add-task](Images/add-task.png)

1. Search for **azure cli** and add an **Azure CLI** task.
1. Search for **azure cli** and add the **Azure CLI** task.

![az-cli-task](Images/az-cli-task.png)

1. Select the newly created task. Select and authorize an Azure subscription. Note you will need to disable popup-blockers to sign in to Azure for authorization. If the pop-up window hangs, please close and try it again.
1. Select the newly created task and authorize your Azure subscription. Note you will need to disable popup-blockers to sign in to Azure for authorization. If the pop-up window hangs, please close and try it again.

![authorize.png](Images/authorize.png)

Expand Down