Skip to content

Commit 2897b62

Browse files
authored
docs(Licensing): Improve information about environment variable limitations
1 parent 75495d6 commit 2897b62

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

deployment/ci-cd-license-key.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,10 +34,18 @@ The Telerik license activation process in CI/CD test, build, staging, and produc
3434

3535
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.
3636

37-
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.
38-
3937
> 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.
4038
39+
### Environment Variable Length Limitations
40+
41+
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:
42+
43+
* 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)
44+
* [GitLab](https://docs.gitlab.com/ci/variables/) (up to 10,000 characters)
45+
46+
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.
47+
48+
4149
## Azure Pipelines
4250

4351
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).

0 commit comments

Comments
 (0)