Skip to content

Update azure-devops.md #6781

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 2 commits into from
Mar 7, 2025
Merged

Update azure-devops.md #6781

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e680d1b
Update azure-devops.md
SeanTarrant Jan 10, 2025
c2e6ecf
Update azure-devops.md
sofietoft Mar 7, 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: 4 additions & 2 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 @@ -164,8 +164,10 @@ It is recommended to handle the `API Key` as a secret. This can be done by ticki
{% endhint %}

{% hint style="info" %}
You can customize the names for the variables as you like, however you then need to rename the affected variables in `azure-release-pipeline.yaml`.
{% endhint %}
You can customize the names for the variables as you like, however, you then need to rename the affected variables in `azure-release-pipeline.yaml`.

Check the references to the variables in the yaml files match the variable syntaxes in the created variable. Example: `umbracoCloudApiKey` = `UMBRACOCLOUDAPIKEY`.
{% endhint %}

When you click on "Save and Run" your first deployment will be triggered. Which means that Azure DevOps is set up with all the needed information to be able to deploy your Cloud project back to Umbraco Cloud.

Expand Down