Skip to content

Script sync update #7107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 28, 2025
Merged

Script sync update #7107

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
849aeff
Rename samples to reflect api version used
jesp209i May 22, 2025
0387b26
mention apply patch pwsh/sh script in samples
jesp209i May 22, 2025
5e3d873
Remove old text
jesp209i May 26, 2025
c023ab1
rewind
jesp209i May 28, 2025
9508688
Merge branch 'script-sync-update' of https://github.com/jesp209i/Umbr…
jesp209i May 28, 2025
db7b62d
Small change to trigger GitBook checks
sofietoft May 28, 2025
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
6 changes: 2 additions & 4 deletions ...cloud/set-up/project-settings/umbraco-cicd/KnownLimitationsAndConsiderations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,9 @@ Attaching a CI/CD pipeline to a flexible environment is currently not possible.
* **Direct Commits to Umbraco Git Repos**: Any commits made directly to the Umbraco-git-repos will cause the process to fail.
* **Remote Build/Test Options**: It is currently not possible to skip the first build step before committing.
* **Incomplete API**:
* The list endpoint lacks filtering capabilities.
* The promotion endpoint for transitioning from dev to stage to live is not fully functional yet.
* The promotion endpoint for transitioning between environments is not fully functional yet.
* **Hotfix Deployments**: Direct deployments to a specific environment are not supported at this time.
* **Lack of Predefined Tasks**: There are no Umbraco-provided Azure DevOps tasks or GitHub Actions available.
* **No Webhooks**: Currently, there's no webhook support for real-time feedback to the pipeline; polling is the only option.
* **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.
* **Documentation Alignment**: We are in the process of updating our documentation to align with standard Umbraco guidelines.
* **Developer Experience**: Plans are underway to create Umbraco-specific Azure DevOps tasks and GitHub Actions to enhance the developer experience.

2 changes: 2 additions & 0 deletions ...o-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,7 @@ For a pipeline that uses Powershell scripts you will need the following files:
* From the `powershell` folder
* `Get-LatestDeployment.ps1`
* `Get-ChangesById.ps1`
* `Apply-Patch.ps1`
* `New-Deployment.ps1`
* `Add-DeploymentPackage.ps1`
* `Start-Deployment.ps1`
Expand Down Expand Up @@ -108,6 +109,7 @@ For a pipeline that uses Bash scripts you will need the following files:
* From the `bash` folder
* `get_latest_deployment.sh`
* `get_changes_by_id.sh`
* `apply-patch.sh`
* `create_deployment.sh`
* `upload_package.sh`
* `start_deployment.sh`
Expand Down
2 changes: 2 additions & 0 deletions ...cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,7 @@ For a pipeline that uses Powershell scripts you will need the following files:
* From the `powershell` folder
* `Get-LatestDeployment.ps1`
* `Get-ChangesById.ps1`
* `Apply-Patch.ps1`
* `New-Deployment.ps1`
* `Add-DeploymentPackage.ps1`
* `Start-Deployment.ps1`
Expand Down Expand Up @@ -160,6 +161,7 @@ For a pipeline that uses Bash scripts you will need the following files:
* From the `bash` folder
* `get_latest_deployment.sh`
* `get_changes_by_id.sh`
* `apply-patch.sh`
* `create_deployment.sh`
* `upload_package.sh`
* `start_deployment.sh`
Expand Down