Skip to content

Commit 1c1442c

Browse files
authored
Merge pull request #7107 from jesp209i/script-sync-update
Script sync update
2 parents 534569e + db7b62d commit 1c1442c

File tree

3 files changed

+6
-4
lines changed

3 files changed

+6
-4
lines changed

umbraco-cloud/set-up/project-settings/umbraco-cicd/KnownLimitationsAndConsiderations.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,11 +29,9 @@ Attaching a CI/CD pipeline to a flexible environment is currently not possible.
2929
* **Direct Commits to Umbraco Git Repos**: Any commits made directly to the Umbraco-git-repos will cause the process to fail.
3030
* **Remote Build/Test Options**: It is currently not possible to skip the first build step before committing.
3131
* **Incomplete API**:
32-
* The list endpoint lacks filtering capabilities.
33-
* The promotion endpoint for transitioning from dev to stage to live is not fully functional yet.
32+
* The promotion endpoint for transitioning between environments is not fully functional yet.
3433
* **Hotfix Deployments**: Direct deployments to a specific environment are not supported at this time.
3534
* **Lack of Predefined Tasks**: There are no Umbraco-provided Azure DevOps tasks or GitHub Actions available.
3635
* **No Webhooks**: Currently, there's no webhook support for real-time feedback to the pipeline; polling is the only option.
3736
* **Casing Conflicts**: Be cautious of casing issues, such as having a README.md file created by Azure DevOps and a `Readme.md` file from the default Umbraco Cloud, as this can cause conflicts in the cloud Git repository.
38-
* **Documentation Alignment**: We are in the process of updating our documentation to align with standard Umbraco guidelines.
39-
* **Developer Experience**: Plans are underway to create Umbraco-specific Azure DevOps tasks and GitHub Actions to enhance the developer experience.
37+

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,7 @@ For a pipeline that uses Powershell scripts you will need the following files:
7777
* From the `powershell` folder
7878
* `Get-LatestDeployment.ps1`
7979
* `Get-ChangesById.ps1`
80+
* `Apply-Patch.ps1`
8081
* `New-Deployment.ps1`
8182
* `Add-DeploymentPackage.ps1`
8283
* `Start-Deployment.ps1`
@@ -108,6 +109,7 @@ For a pipeline that uses Bash scripts you will need the following files:
108109
* From the `bash` folder
109110
* `get_latest_deployment.sh`
110111
* `get_changes_by_id.sh`
112+
* `apply-patch.sh`
111113
* `create_deployment.sh`
112114
* `upload_package.sh`
113115
* `start_deployment.sh`

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/github-actions.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,7 @@ For a pipeline that uses Powershell scripts you will need the following files:
127127
* From the `powershell` folder
128128
* `Get-LatestDeployment.ps1`
129129
* `Get-ChangesById.ps1`
130+
* `Apply-Patch.ps1`
130131
* `New-Deployment.ps1`
131132
* `Add-DeploymentPackage.ps1`
132133
* `Start-Deployment.ps1`
@@ -160,6 +161,7 @@ For a pipeline that uses Bash scripts you will need the following files:
160161
* From the `bash` folder
161162
* `get_latest_deployment.sh`
162163
* `get_changes_by_id.sh`
164+
* `apply-patch.sh`
163165
* `create_deployment.sh`
164166
* `upload_package.sh`
165167
* `start_deployment.sh`

0 commit comments

Comments
 (0)