Skip to content
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,14 @@

For GitHub, see the [Skip cloud-sync in GitHub](troubleshooting.md#skip-cloud-sync-in-github) section.

With a few clicks you can manually trigger a pipeline to run without the cloud-sync:
Navigate to your azure-release-pipeline.yaml and comment out 35 and 36. More specifically these two lines:

Check warning on line 79 in umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐶 [UmbracoDocs.Brands] Use 'Azure' instead of 'azure' for brand consistency. Raw Output: {"message": "[UmbracoDocs.Brands] Use 'Azure' instead of 'azure' for brand consistency.", "location": {"path": "umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md", "range": {"start": {"line": 79, "column": 18}}}, "severity": "WARNING"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please but code tags around file names 🙏

Suggested change
Navigate to your azure-release-pipeline.yaml and comment out 35 and 36. More specifically these two lines:
Navigate to your `azure-release-pipeline.yaml` and comment out the following lines:

```sh
dependsOn: cloudSyncStage
condition: in(dependencies.cloudSyncStage.result, 'Succeeded', 'Skipped')
```

Trigger a code deployment and make sure to uncheck the "Umbraco Cloud Sync" stage as mentioned below.
~~With a few clicks you can manually trigger a pipeline to run without the cloud-sync:~~

1. Ensure that your Azure DevOps repository is up to date with any changes in your Umbraco Cloud environment.
2. Find the pipeline in Azure DevOps.
Expand Down
Loading