Skip to content

docs(Licensing): Improve information about environment variable limitations #3319

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
Oct 31, 2025
Merged

docs(Licensing): Improve information about environment variable limitations #3319

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2897b62
docs(Licensing): Improve information about environment variable limit…
dimodi Oct 31, 2025
6fb313b
Update deployment/ci-cd-license-key.md
dimodi Oct 31, 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
12 changes: 10 additions & 2 deletions deployment/ci-cd-license-key.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,10 +34,18 @@ The Telerik license activation process in CI/CD test, build, staging, and produc

In most cases, the recommended way to provide your license key to the `Telerik.Licensing` NuGet package in CI/CD environments is to use one of the available environment variables.

Use `TELERIK_LICENSE_PATH` or [only a license file](slug:installation-license-key#manual-installation) on Windows and Windows Server machines, which are managed directly through the operating system's user interface. Do not use the `TELERIK_LICENSE` environment variable in this case, due to the large variable value length.

> Treat the license key and the license file as secrets. Always store and retrieve them in a secure manner, according to the build platform's best practices.

## Environment Variable Length Limitations

The Telerik license key size depends on the number of licenses it includes, including renewals. Some environments may have a limit on the environment variable size, which is smaller than your Telerik license key length. Such examples include:

* Windows and Windows Server machines (up to 32,767 characters for all environment variables and much smaller limits for setting variables in the Registry or the system settings)
* [GitLab](https://docs.gitlab.com/ci/variables/) (up to 10,000 characters)

In such cases, use `TELERIK_LICENSE_PATH` or [only a license file](slug:installation-license-key#manual-installation) instead of `TELERIK_LICENSE`. The `TELERIK_LICENSE_PATH` must point to the Telerik license file location, including the `telerik-license.txt` file name. The license file must be stored and provided to the deployment pipeline in a secure manner.


## Azure Pipelines

Azure Pipelines provides built-in tools to store and use secret environment variables and secure files. The recommended option with **Classic** pipelines is to [download the Telerik license file as a secure file](#use-telerik_license_path).
Expand Down
Loading