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: umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/advanced-deployment-options.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Advanced Setup: Deployment options
2
2
3
-
In this example, you will learn how to use the deployment options available with the v2 endpoints for CI/CD.
3
+
Here you will learn how to use the deployment options available with the v2 endpoints for CI/CD.
4
4
5
-
This provides some control to the deployment process.
5
+
This provides some control to the CI/CD deployment process within the isolated instance before your code hits the website.
6
6
7
7
## Option: skipVersionCheck
8
8
@@ -16,9 +16,9 @@ Enabling this option will skip that check and let any deployments with downgrade
16
16
17
17
The Umbraco CI/CD Flow runs the deployment in an isolated instance before doing the actual deployment to cloud. In the isolated instance we will try to do a `Dotnet restore` and `Dotnet build` of the incoming solution. This is a safeguard to prevent CI/CD isolated instance from sending broken code to the Umbraco Cloud environment.
18
18
19
-
Enabling this option will skip the `restore` and `build` process in the isolated instance. This can take a couple of minutes of the deployment process.
19
+
Enabling this option will skip the `restore` and `build` process in the isolated instance. This can shorten the deployment process with a couple of minutes.
20
20
21
-
The final deployment on the actual website still runs it's own Restoreand Build, which cannot be skipped.
21
+
Keep in mind that the final KUDU deployment on the actual website still runs it's own **Restore**, **Build**and **Publish**, which cannot be skipped.
0 commit comments