You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: articles/devops-project/azure-devops-project-nodejs.md
+70-41
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Create a CI/CD pipeline for Node.js with the Azure DevOps Project | Quickstart
3
-
description: The DevOps Project makes it easy to get started on Azure. It helps you launch an app on an Azure service of your choice in few quick steps.
2
+
title: 'Quickstart: Create a CI/CD pipeline for Node.js with Azure DevOps Projects'
3
+
description: DevOps Projects makes it easy to get started on Azure. It helps you launch an app on an Azure service of your choice in few quick steps.
4
4
ms.prod: devops
5
5
ms.technology: devops-cicd
6
6
services: vsts
@@ -20,103 +20,132 @@ monikerRange: 'vsts'
20
20
---
21
21
22
22
23
-
# Create a CI/CD pipeline for Node.js with the Azure DevOps Project
23
+
# Create a CI/CD pipeline for Node.js with Azure DevOps Projects
24
24
25
-
The Azure DevOps Project presents a simplified experience which creates Azure resources and sets up a continuous integration (CI) and continuous delivery (CD) pipeline for your Node.js app in Azure DevOps Services.
25
+
Azure DevOps Projects presents a simplified experience that creates Azure resources and sets up a continuous integration (CI) and continuous delivery (CD) pipeline for your Node.js app in Azure Pipelines.
26
26
27
27
If you don't have an Azure subscription, you can get one free through [Visual Studio Dev Essentials](https://visualstudio.microsoft.com/dev-essentials/).
28
28
29
29
## Sign in to the Azure portal
30
30
31
-
The Azure DevOps Project creates a CI/CD pipeline in Azure. You can create a free **new Azure DevOps Services**organization or use an **existing organization**. The DevOps Project also creates **Azure resources** in the **Azure subscription** of your choice.
31
+
DevOps Projects creates a CI/CD pipeline in Azure Pipelines. You can create a new Azure DevOps organization or use an existing organization. DevOps Projects also creates Azure resources in the Azure subscription of your choice.
32
32
33
-
1. Sign into the [Microsoft Azure portal](https://portal.azure.com).
33
+
1. Sign in to the [Microsoft Azure portal](https://portal.azure.com).
34
34
35
-
1.Choose the **Create a resource** icon in the left navigation bar, then search for **DevOps Project**. Choose **Create**.
35
+
1.In the left pane, select **Create a resource**, and then search for **DevOps Projects**.
1. Select the **Node.js** sample application. The Node.js samples include a choice of several application frameworks.
41
+
1. Select the Node.js sample application.
42
+
The Node.js samples include a choice of several application frameworks.
42
43
43
-
1. The default sample framework is **Express.js**. Leave the default setting, and choose **Next**.
44
+
1. The default sample framework is Express.js. Leave the default setting, and then select **Next**.
45
+
**Web App on Windows** is the default deployment target. The application framework, which you chose previously, dictates the type of Azure service deployment target available here.
44
46
45
-
1.**Web App on Windows** is the default deployment target. The application framework, which you chose on the previous steps, dictates the type of Azure service deployment target available here. Leave the default service, and then choose**Next**.
47
+
2.Leave the default service, and then select**Next**.
46
48
47
-
## Configure Azure DevOps Services and an Azure subscription
49
+
## Configure Azure DevOps and an Azure subscription
48
50
49
-
1. Create a **new** Azure DevOps Services organization or choose an **existing** organization. Choose a **name** for your Azure DevOps project. Select your **Azure subscription**, **location**, and choose a **name** for your application. When you're done, choose **Done**.
51
+
1. Create a new Azure DevOps organization or choose an existing organization.
50
52
51
-
1. In a few minutes, the **Azure DevOps Project dashboard** loads in the Azure portal. A sample application is set up in a repository in your Azure DevOps Services organization, a build executes, and your application deploys to Azure. This dashboard provides visibility into your **code repository**, **Azure CI/CD pipeline**, and your **application in Azure**. On the right side of the dashboard, select **Browse** to view your running application.
53
+
a. Choose a name for your project.
54
+
55
+
b. Select your Azure subscription and location, choose a name for your application, and then select **Done**.
56
+
After a few minutes, the DevOps Projects dashboard is displayed in the Azure portal. A sample application is set up in a repository in your Azure DevOps organization, a build is executed, and your application is deployed to Azure. This dashboard provides visibility into your code repository, the CI/CD pipeline, and your application in Azure.
57
+
58
+
3. Select **Browse** to view your running application.
The Azure DevOps Project automatically configures a CI build and release trigger. You're now ready to collaborate with a team on a Node.js app with a CI/CD process that automatically deploys your latest work to your web site.
62
+
DevOps Projects automatically configured a CI build and release trigger. You're now ready to collaborate with a team on a Node.js app with a CI/CD process that automatically deploys your latest work to your web site.
56
63
57
64
## Commit code changes and execute CI/CD
58
65
59
-
The Azure DevOps Project created a Git repository in your Azure DevOps Services organization or GitHub account. Follow the steps below to view the repository and make code changes to your application.
66
+
DevOps Projects creates a Git repository in Azure Repos or GitHub. Take the following steps to view the repository and make code changes to your application.
60
67
61
-
1. On the left-hand side of the DevOps Project dashboard, select the link for your **master** branch. This link opens a view to the newly created Git repository.
68
+
1. On the left of the DevOps Projects dashboard, select the link for your master branch.
69
+
This link opens a view to the newly created Git repository.
62
70
63
-
1. To view the repository clone URL, select **Clone** from the top right of the browser. You can clone your Git repository in your favorite IDE. In the next few steps, you can use the web browser to make and commit code changes directly to the master branch.
71
+
1. To view the repository clone URL, select **Clone** on the top right of the browser.
72
+
You can clone your Git repository in your favorite IDE. In the next few steps, you can use the web browser to make and commit code changes directly to the master branch.
64
73
65
-
1. On the left-hand side of the browser, navigate to the **views/index.pug** file.
74
+
1. On the left side of the browser, go to the **views/index.pug** file.
66
75
67
-
1. Select **Edit**, and make a change to the h2 heading. For example, type **Get started right away with the Azure DevOps Project** or make some other change.
76
+
1. Select **Edit**, and then make a change to the h2 heading.
77
+
For example, type **Get started right away with the Azure DevOps Project** or make some other change.
68
78
69
-
1.Choose**Commit**, then save your changes.
79
+
1.Select**Commit**, and then save your changes.
70
80
71
-
1. In your browser, navigate to the **Azure DevOps Project dashboard**. You should now see a build is in progress. The changes you just made are automatically built and deployed via an Azure CI/CD pipeline.
81
+
1. In your browser, go to the DevOps Projects dashboard.
82
+
You should now see a build in progress. The changes you just made are automatically built and deployed via a CI/CD pipeline.
72
83
73
84
## Examine the Azure CI/CD pipeline
74
85
75
-
The Azure DevOps Project automatically configured a full Azure CI/CD pipeline in your Azure DevOps Services organization. Explore and customize the pipeline as needed. Follow the steps below to familiarize yourself with the Azure DevOps Services build and release pipelines.
86
+
In the previous step, DevOps Projects automatically configured a full CI/CD pipeline. Explore and customize the pipeline as needed. Take the following steps to familiarize yourself with the build and release pipelines.
76
87
77
-
1. Select **Build Pipelines** from the **top** of the Azure DevOps Project dashboard. This link opens a browser tab and opens the Azure DevOps Services build pipeline for your new project.
88
+
1. At the top of the DevOps Projects dashboard, select **Build Pipelines**.
89
+
This link opens a browser tab and the build pipeline for your new project.
78
90
79
-
1. Move the mouse cursor to the right of the build pipeline next to the **Status** field. Select the **ellipsis** that appears. This action opens a menu where you can start several activities such as queue a new build, pause a build, and edit the build pipeline.
91
+
1. Point to the **Status** field, and then select the ellipsis (...).
92
+
This action opens a menu where you can start several activities such as queuing a new build, pausing a build, and editing the build pipeline.
80
93
81
94
1. Select **Edit**.
82
95
83
-
1. From this view, **examine the various tasks** for your build pipeline. The build executes various tasks such as fetching sources from the Git repository, restoring dependencies, and publishing outputs used for deployments.
96
+
1. In this pane, you can examine the various tasks for your build pipeline.
97
+
The build performs a variety of tasks such as fetching sources from the Git repository, restoring dependencies, and publishing outputs that are used for deployments.
98
+
99
+
1. At the top of the build pipeline, select the build pipeline name.
84
100
85
-
1.At the top of the build pipeline, select the **build pipeline name**.
101
+
1.Change the name of your build pipeline to something more descriptive, select **Save & queue**, and then select **Save**.
86
102
87
-
1. Change the **name** of your build pipeline to something more descriptive. Select **Save & queue**, then select **Save**.
103
+
1. Under your build pipeline name, select **History**.
104
+
In the **History** pane, you see an audit trail of your recent changes for the build. Azure Pipelines keeps track of any changes that are made to the build pipeline, and it allows you to compare versions.
88
105
89
-
1. Under your build pipeline name, select **History**. You see an audit trail of your recent changes for the build. Azure DevOps Services keeps track of any changes made to the build pipeline, and allows you to compare versions.
106
+
1. Select **Triggers**.
107
+
DevOps Projects automatically created a CI trigger, and every commit to the repository starts a new build. You can optionally choose to include or exclude branches from the CI process.
90
108
91
-
1. Select **Triggers**. The Azure DevOps Project automatically created a CI trigger, and every commit to the repository starts a new build. You can optionally choose to include or exclude branches from the CI process.
109
+
1. Select **Retention**.
110
+
Depending on your scenario, you can specify policies to keep or remove a certain number of builds.
92
111
93
-
1. Select **Retention**. Based on your scenario, you can specify policies to keep or remove a certain number of builds.
112
+
1. Select **Build and Release**, and then select **Releases**.
113
+
DevOps Projects creates a release pipeline to manage deployments to Azure.
94
114
95
-
1. Select **Build and Release**, then choose **Releases**. The Azure DevOps Project created an Azure DevOps Services release pipeline to manage deployments to Azure.
115
+
1. On the left, select the ellipsis (...) next to your release pipeline, and then select **Edit**.
116
+
The release pipeline defines the release process.
96
117
97
-
1. On the left-hand side of the browser, select the **ellipsis** next to your release pipeline, then choose **Edit**.
118
+
12. Under **Artifacts**, select **Drop**.
119
+
The build pipeline you examined in the previous steps produces the output used for the artifact.
98
120
99
-
1. The release pipeline contains a **pipeline**, which defines the release process. Under **Artifacts**, select **Drop**. The build pipeline you examined in the previous steps produces the output used for the artifact.
121
+
1. Next to the **Drop** icon, select the **Continuous deployment trigger**.
122
+
This release pipeline has an enabled CD trigger, which runs a deployment every time there is a new build artifact available. Optionally, you can disable the trigger so that your deployments require manual execution.
100
123
101
-
1. To the right-hand side of the **Drop** icon, select the **Continuous deployment trigger**. This release pipeline has an enabled CD trigger, which executes a deployment every time there is a new build artifact available. Optionally, you can disable the trigger, so your deployments require manual execution.
102
124
103
-
1. On the left-hand side of the browser, select **Tasks**. The tasks are the activities your deployment process performs. In this example, a task was created to deploy to **Azure App service**.
125
+
1. On the left, select **Tasks**.
126
+
The tasks are the activities that your deployment process performs. In this example, a task was created to deploy to Azure App Service.
104
127
105
-
1. On the right-hand side of the browser, select **View releases**. This view shows a history of releases.
106
128
107
-
1. Select the **ellipsis** next to one of your releases, and choose **Open**. There are several menus to explore from this view such as a release summary, associated work items, and tests.
129
+
1. On the right, select **View releases**.
130
+
This view shows a history of releases.
108
131
109
-
1. Select **Commits**. This view shows code commits associated with the specific deployment.
132
+
1. Select the ellipsis (...) next to one of your releases, and then select **Open**.
133
+
There are several menus to explore, such as a release summary, associated work items, and tests.
110
134
111
-
1. Select **Logs**. The logs contain useful information about the deployment process. They can be viewed both during and after deployments.
135
+
1. Select **Commits**.
136
+
This view shows code commits that are associated with the specific deployment.
137
+
138
+
1. Select **Logs**.
139
+
The logs contain useful information about the deployment process. They can be viewed both during and after deployments.
112
140
113
141
## Clean up resources
114
142
115
-
When no longer needed, you can delete the Azure App service and related resources created in this quickstart by using the **Delete** functionality on the Azure DevOps Project dashboard.
143
+
You can delete Azure App Service and other related resources that you created when you don't need them anymore. Use the **Delete** functionality on the DevOps Projects dashboard.
144
+
116
145
117
146
## Next steps
118
147
119
-
When you configured your CI/CD process in this quickstart, a build and release pipeline were automatically created in your Azure DevOps Project. You can modify these build and release pipelines to meet the needs of your team. To learn more see this tutorial:
148
+
When you configured your CI/CD process, build and release pipelines were automatically created. You can modify these build and release pipelines to meet the needs of your team. To learn more about the CI/CD pipeline, see:
120
149
121
150
> [!div class="nextstepaction"]
122
151
> [Customize CD process](https://docs.microsoft.com/azure/devops/pipelines/release/define-multistage-release-process?view=vsts)
0 commit comments