You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployment/ci-cd-license-key.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,8 @@ Azure Pipelines provides built-in tools to store and use secret environment vari
57
57
1. Map the secret variable to a new environment variable named `TELERIK_LICENSE`.
58
58
1. Use the `TELERIK_LICENSE` environment variable in the tasks, steps, or scripts that build and publish the Blazor app. **Classic** pipelines may need to [set an output variable to share and consume the license key in multiple steps](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/set-variables-scripts?view=azure-devops&tabs=bash#set-an-output-variable-for-use-in-future-jobs).
59
59
60
+
In the following example, replace `Secret_Telerik_License_Key` with the actual pipeline variable name.
61
+
60
62
>caption Using a TELERIK_LICENSE environment variable in Azure Pipeline YAML
0 commit comments