Skip to content

Commit f1a1b1e

Browse files
committed
GitHub CICD migrate to V2
1 parent 5957687 commit f1a1b1e

File tree

1 file changed

+45
-1
lines changed
  • umbraco-cloud/set-up/project-settings/umbraco-cicd

1 file changed

+45
-1
lines changed

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

Lines changed: 45 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,4 +65,48 @@ You need to replace `##Your project Id here##` with the project Id and the value
6565

6666
You can use any of the available aliases, but to get similar functionality as before you should select the environment described as `Leftmost mainline`.
6767

68-
# GitHub
68+
# Migrate GitHub
69+
Start by deleting the scripts and yaml files you initially got from the CICD samples:
70+
- Delete the Yaml:
71+
- `main.yml`
72+
- `cloud-sync.yml`
73+
- `cloud-deployment.yml`
74+
75+
You probably only have either PowerShell or Bash.
76+
- PowerShell files to delete:
77+
- `Add-DeploymentPackage.ps1`
78+
- `Apply-Patch.ps1`
79+
- `Get-ChangesById.ps1`
80+
- `Get-LatestDeployment.ps1`
81+
- `New-Deployment.ps1`
82+
- `Start-Deployment.ps1`
83+
- `Test-Deployment.ps1`
84+
- Bash files to delete:
85+
- `apply_patch.sh`
86+
- `create_deployment.sh`
87+
- `get_changes_by_id.sh`
88+
- `get_deployment_status.sh`
89+
- `get_latest_deployment.sh`
90+
- `start_deployment.sh`
91+
- `upload_package.sh`
92+
93+
Now copy the scripts from the sample repositorys V2 folder to the corresponding folder in you repo:
94+
- If you prefer PowerShell:
95+
- All .ps1 files in `V2/powershell` should be copied to `.github/powershell`
96+
- All .yaml/.yml in `V2/powershell/github` should be copied to `.github/workflows`
97+
- If you prefer Bash:
98+
- All .sh files in `V2/bash` should be copied to `.github/scripts`
99+
- All .yaml/.yml in `V2/bash/github` should be copied to `.github/workflows`
100+
101+
Now we need one important value: Target environment alias.
102+
- [This section](./samplecicdpipeline/README.md#getting-environment-aliases-to-target) explains how to get the environment alias.
103+
104+
Go to your GitHub repository and enter the `Settings` section.
105+
- In the left side menu find the `Security` section and click on `Actions`
106+
- Click on the tab `Variables`
107+
- Click on `New repository variable`
108+
- Call the variable `TARGET_ENVIRONMENT_ALIAS`
109+
- Use the environment alias as value
110+
- Click on `Add variable`.
111+
112+
You can use any of the available aliases, but to get similar functionality as before you should select the environment described as `Leftmost mainline`.

0 commit comments

Comments
 (0)