Adding the License Key to CI/CD Services
This article describes how to set up and activate your Telerik Reporting license key across a few popular CI services by using environment variables.
When working with CI/CD platforms, always add the Telerik.Licensing
NuGet package as a project dependency. This package activates Telerik Reporting at build time by using the provided license key.
The license activation process in a CI/CD environment involves the following steps:
- Download a license key from your Telerik account.
- Add the
Telerik.Licensing
NuGet package as a project dependency:<PackageReference Include="Telerik.Licensing" Version="1.*" />
-
Create an environment variable named
TELERIK_LICENSE
and add your Telerik Reporting license key as a value.
Creating an Environment Variable
The recommended approach for providing your license key to the Telerik.Licensing
NuGet package is to use environment variables. Each CI/CD platform has a different process for setting environment variables and this article lists only some of the most popular examples.
Azure Pipelines (YAML)
- Create a new User-defined Variable named
TELERIK_LICENSE
. - Paste the contents of the license key file as a value.
Azure Pipelines (Classic)
- Create a new user-defined variable named
TELERIK_LICENSE
. - Paste the contents of the license key file as a value.
GitHub Actions
- Create a new Repository Secret or an Organization Secret.
- Set the name of the secret to
TELERIK_LICENSE
and paste the contents of the license file as a value. -
After running
npm install
oryarn
, add a build step to activate the license:env: TELERIK_LICENSE: ${{ secrets.TELERIK_LICENSE }}