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: docs/spfx/toolchain/implement-ci-cd-with-azure-pipelines.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,14 @@ Azure Pipelines is the newer version of the Azure DevOps build and release featu
11
11
This article explains the steps involved in setting up your Azure Pipelines environment with Continuous Integration and Continuous Deployment to automate your SharePoint Framework builds, unit tests, and deployment.
12
12
13
13
> [!NOTE]
14
-
> Azure Multi-stage Pipelines is still in preview and you need to make sure you enable this preview feature for your Azure DevOps organization under __Preview Features__
14
+
> Azure Multi-stage Pipelines is still in preview and you need to make sure you [enable this preview feature](https://docs.microsoft.com/en-us/azure/devops/project/navigation/preview-features) for your Azure DevOps organization under __Preview Features__.
15
15
16
16
## Choosing between Azure Multi-stage Pipelines (preview) and Azure DevOps builds and releases
17
17
18
18
There are currently two approaches available to implement continuous integration, and deployement in Azure DevOps.
19
19
Azure builds and releases is the historic one, featuring a graphical edition experience and storing the definitions in a JSON document hidden from the user.
20
20
21
-
Azure multi-stage Pipelines is a newer feature still in preview, is relies on pipeline definitions stored as YAML files on the repository providing transparency, version history and repeatability.
21
+
Azure multi-stage Pipelines is a newer feature still in preview, is relies on pipeline definitions stored as YAML files on the repository providing transparency, version history, and repeatability.
22
22
Both approaches are described for the SharePoint Framework:
23
23
24
24
-[Azure Build and Release](./implement-ci-cd-with-azure-devops.md)
@@ -213,4 +213,4 @@ To create the variable group, follow these steps:
213
213
- o365_app_catalog_site_url: the url of the app catalog site collection
214
214
215
215
> [!NOTE]
216
-
> You can select the lockpad icon next to the variable value input to mark it as sensitive and have Azure DevOps hide the value from other users and from the logs.
216
+
> You can select the lockpad icon next to the variable value input to mark it as sensitive and have Azure DevOps hide the value from other users and from the logs.
0 commit comments