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/troubleshooting.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the dep
12
12
13
13
### Deployment reports: No changes detected - cleaning up
14
14
15
-
The package you uploaded didn't contain any changes that would affect the git repository on the Cloud Environment. The CICD job will skip the rest of its usual steps and complete.
15
+
The package you uploaded didn't contain any changes that would affect the git repository on the Cloud Environment. The CI/CD job will skip the rest of its usual steps and complete.
16
16
17
17
If the expected that the deployment should create a change to the Cloud Environment, please make sure that you are uploading the correct zip file.
18
18
@@ -182,13 +182,13 @@ Once the marker file is removed, run your pipeline again.
182
182
### Unable to verify Deployment has finished
183
183
184
184
This error will be shown when the system is unable to verify the latest deployment is pushed and deployed in Kudu.
185
-
When a change is pushed to a Cloud Environment the Kudu deployment is started. CICD is also utilizing this flow.
185
+
When a change is pushed to a Cloud Environment the Kudu deployment is started. CI/CD is also utilizing this flow.
186
186
187
187
A couple of steps to try:
188
-
-make sure your code can compile and run (mostly relevant if you are using the skipBuildAndRestore toggle in V2)
189
-
-running npm commands via csproj files is generally unsupported on Umbraco Cloud
190
-
-create and commit a small change and try deploying again
191
-
-a small change can be adding a dummy text file next to you code files or adding a comment in a cs file.
188
+
-Make sure your code can compile and run (relevant only if you haver enabled the skipBuildAndRestore toggle in V2)
189
+
-Running npm commands via csproj files is generally unsupported on Umbraco Cloud
190
+
-Create and commit a small change and try deploying again
191
+
-A small change can be adding a dummy text file next to you code files or adding a comment in a cs file.
0 commit comments