From 41b18481281d01a64643921b9347bd66915b4e9c Mon Sep 17 00:00:00 2001 From: Jesper Madsen Date: Thu, 25 Sep 2025 12:26:55 +0200 Subject: [PATCH 01/11] 56681 CICD Verify Deployment --- .../umbraco-cicd/troubleshooting.md | 21 +++++++++++++++++-- .../umbraco-cicd/umbracocloudapi.md | 8 +++++-- 2 files changed, 25 insertions(+), 4 deletions(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 78c257c870f..5989326d314 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -10,6 +10,12 @@ The reason for this is that the KUDU deploy process fails. This process takes th To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the deployments to go through as expected. +### Deployment reports: No changes detected - cleaning up + +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. + +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. + ## Cloud Sync ### The projects left-most mainline environment has changed @@ -163,16 +169,27 @@ In rare cases deployments fail, and the cloud infrastructure doesn't clean up co In order to fix this issue, you need to use [KUDU](../../../optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools/) to remove the leftover marker file. -1. Access KUDU on the "left-most" environment +1. Access KUDU on the affected environment * If you only have one environment you want the live environment -* If you have more than one environment, you want the left-most mainline environment +* If you use V1 endpoints and have more than one environment, you want the left-most mainline environment 3. Navigate to `site` > `locks` folder In there, there should be a file named `updating` 4. Remove the `updating` file. Once the marker file is removed, run your pipeline again. +### Unable to verify Deployment has finished + +This error will be shown when the system is unable to verify the latest deployment is pushed and deployed in Kudu. +When a change is pushed to a Cloud Environment the Kudu deployment is started. CICD is also utilizing this flow. + +A couple of steps to try: +- make sure your code can compile and run (mostly relevant if you are using the skipBuildAndRestore toggle in V2) +- running npm commands via csproj files is generally unsupported on Umbraco Cloud +- create and commit a small change and try deploying again + - a small change can be adding a dummy text file next to you code files or adding a comment in a cs file. + ## Environment errors after deployment ### Unable to determine environment by its {environment-id} diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md index ed6a4d2a931..ac6f2c52b5c 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md @@ -277,7 +277,8 @@ Should the deployment fail, check the `deploymentStatusMessages` for more inform ], "createdUtc": string, "completedUtc":string, - "modifiedUtc": string + "modifiedUtc": string, + "cloudRepositoryUpdated": boolean } ``` @@ -285,7 +286,9 @@ Should the deployment fail, check the `deploymentStatusMessages` for more inform ### Get Deployments -The endpoint lets you retrieve a list of completed deployments. It can only list deployments that have been run through the api. +The endpoint lets you retrieve a list of deployments that have created a change in the git repository of the Cloud Environment. Deployment can have state 'Completed' or 'Failed'. + +It can only list deployments that have been run through the api. The API allows you to filter and limit the number of returned deployments using query parameters: @@ -327,6 +330,7 @@ The response from this API call will return an object containing a list of deplo "createdUtc": string, "modifiedUtc": string, "completedUtc": string, + "cloudRepositoryUpdated": boolean } ], "totalItems": number, From 8760b1c924a6f1fb6329c81d16d29e05c9b2d7d5 Mon Sep 17 00:00:00 2001 From: Jesper Madsen Date: Thu, 25 Sep 2025 12:31:37 +0200 Subject: [PATCH 02/11] We do support CICD to flexible environments --- .../umbraco-cicd/README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md index 8b621f93692..2babcde7503 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md @@ -20,10 +20,6 @@ Explore the practical benefits of using Umbraco CI/CD Flow for your development * Umbraco CI/CD Flow allows for greater scalability and flexibility in your deployment process. You can adapt your existing CI/CD pipeline to handle larger projects or more complex workflows without having to overhaul your Umbraco Cloud setup. -{% hint style="info" %} -Attaching a CI/CD pipeline to a flexible environment is currently not possible. The CI/CD workflow must go through the mainline deployment workflow. -{% endhint %} - **Centralized Management** * With Umbraco CI/CD Flow, you can centralize the management of your deployments, tests, and workflows. This makes it easier to monitor, troubleshoot, and optimize your processes, leading to more efficient and reliable deployments. Automating deployment minimizes the risk for human errors that could have a negative effect on the target environment. From b873bb9e30dfac12de80035351c108a7b3e16cfd Mon Sep 17 00:00:00 2001 From: Jesper Madsen Date: Thu, 25 Sep 2025 12:43:37 +0200 Subject: [PATCH 03/11] review dog revisions --- .../umbraco-cicd/troubleshooting.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 5989326d314..61b83e61f70 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -12,7 +12,7 @@ To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the dep ### Deployment reports: No changes detected - cleaning up -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. +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. 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. @@ -182,13 +182,13 @@ Once the marker file is removed, run your pipeline again. ### Unable to verify Deployment has finished This error will be shown when the system is unable to verify the latest deployment is pushed and deployed in Kudu. -When a change is pushed to a Cloud Environment the Kudu deployment is started. CICD is also utilizing this flow. +When a change is pushed to a Cloud Environment the Kudu deployment is started. CI/CD is also utilizing this flow. A couple of steps to try: -- make sure your code can compile and run (mostly relevant if you are using the skipBuildAndRestore toggle in V2) -- running npm commands via csproj files is generally unsupported on Umbraco Cloud -- create and commit a small change and try deploying again - - a small change can be adding a dummy text file next to you code files or adding a comment in a cs file. +- Make sure your code can compile and run (relevant only if you haver enabled the skipBuildAndRestore toggle in V2) +- Running npm commands via csproj files is generally unsupported on Umbraco Cloud +- Create and commit a small change and try deploying again + - A small change can be adding a dummy text file next to you code files or adding a comment in a cs file. ## Environment errors after deployment From 69a380cd17a4699610a460a39cc94a392ffd6034 Mon Sep 17 00:00:00 2001 From: Jesper Madsen Date: Thu, 25 Sep 2025 12:49:21 +0200 Subject: [PATCH 04/11] typo --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 61b83e61f70..c0e1710fe84 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -185,7 +185,7 @@ This error will be shown when the system is unable to verify the latest deployme When a change is pushed to a Cloud Environment the Kudu deployment is started. CI/CD is also utilizing this flow. A couple of steps to try: -- Make sure your code can compile and run (relevant only if you haver enabled the skipBuildAndRestore toggle in V2) +- Make sure your code can compile and run (relevant only if you have enabled the skipBuildAndRestore toggle in V2) - Running npm commands via csproj files is generally unsupported on Umbraco Cloud - Create and commit a small change and try deploying again - A small change can be adding a dummy text file next to you code files or adding a comment in a cs file. From feed86b2ff0f388e7ecb6c3b446305b6cdd353ce Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:17:13 +0200 Subject: [PATCH 05/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index c0e1710fe84..d26e91aaff4 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -12,7 +12,7 @@ To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the dep ### Deployment reports: No changes detected - cleaning up -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. +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 remaining steps and complete. 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. From 7cd100ebaefad5428dc4499d80192d1322ecfb9c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:17:23 +0200 Subject: [PATCH 06/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index d26e91aaff4..0e2e070d663 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -14,7 +14,7 @@ To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the dep 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 remaining steps and complete. -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. +If you expected the deployment to create changes in the Cloud Environment, make sure you are uploading the correct ZIP file. ## Cloud Sync From 49da309c82488c07ac5740ce2454e8a57f0b50d3 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:17:32 +0200 Subject: [PATCH 07/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 0e2e070d663..3ee7ecd0077 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -181,7 +181,7 @@ Once the marker file is removed, run your pipeline again. ### Unable to verify Deployment has finished -This error will be shown when the system is unable to verify the latest deployment is pushed and deployed in Kudu. +This error will be shown when the system is unable to verify that the latest deployment has been pushed and deployed in Kudu. When a change is pushed to a Cloud Environment the Kudu deployment is started. CI/CD is also utilizing this flow. A couple of steps to try: From 69176b33b48a5687a2475847518b5c42d40acab0 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:17:40 +0200 Subject: [PATCH 08/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 3ee7ecd0077..47832f3fc38 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -185,7 +185,7 @@ This error will be shown when the system is unable to verify that the latest dep When a change is pushed to a Cloud Environment the Kudu deployment is started. CI/CD is also utilizing this flow. A couple of steps to try: -- Make sure your code can compile and run (relevant only if you have enabled the skipBuildAndRestore toggle in V2) +- Make sure your code can compile and run (relevant only if you have enabled the `skipBuildAndRestore` toggle in V2) - Running npm commands via csproj files is generally unsupported on Umbraco Cloud - Create and commit a small change and try deploying again - A small change can be adding a dummy text file next to you code files or adding a comment in a cs file. From 7c7f164db2da6f1108c5d591f4e8396bb4dbaba9 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:17:47 +0200 Subject: [PATCH 09/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index 47832f3fc38..f8a19b599ea 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -186,7 +186,7 @@ When a change is pushed to a Cloud Environment the Kudu deployment is started. C A couple of steps to try: - Make sure your code can compile and run (relevant only if you have enabled the `skipBuildAndRestore` toggle in V2) -- Running npm commands via csproj files is generally unsupported on Umbraco Cloud +- Running npm commands via `.csproj` files is generally unsupported on Umbraco Cloud - Create and commit a small change and try deploying again - A small change can be adding a dummy text file next to you code files or adding a comment in a cs file. From 06d3e7f774107ee460226cf29f097aaaa3a4c25c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:18:44 +0200 Subject: [PATCH 10/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md --- .../umbraco-cicd/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md index f8a19b599ea..27270a02fe3 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md @@ -188,7 +188,7 @@ A couple of steps to try: - Make sure your code can compile and run (relevant only if you have enabled the `skipBuildAndRestore` toggle in V2) - Running npm commands via `.csproj` files is generally unsupported on Umbraco Cloud - Create and commit a small change and try deploying again - - A small change can be adding a dummy text file next to you code files or adding a comment in a cs file. + - A small change can be adding a dummy text file next to your code files or adding a comment in a `.cs` file. ## Environment errors after deployment From 92cc42c3e61d1d6b44cd990e442e3142c5f015f3 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:18:51 +0200 Subject: [PATCH 11/11] Update umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md --- .../umbraco-cicd/umbracocloudapi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md index ac6f2c52b5c..13a14bb3934 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/umbracocloudapi.md @@ -286,9 +286,9 @@ Should the deployment fail, check the `deploymentStatusMessages` for more inform ### Get Deployments -The endpoint lets you retrieve a list of deployments that have created a change in the git repository of the Cloud Environment. Deployment can have state 'Completed' or 'Failed'. +The endpoint retrieves a list of deployments that have created a change in the Git repository of the cloud environment. A deployment can have the state **Completed** or **Failed**. -It can only list deployments that have been run through the api. +It only lists deployments that have been run through the API. The API allows you to filter and limit the number of returned deployments using query parameters: