Adding the License Key to CI/CD Services

This article describes how to set up and activate your Telerik UI for WPF license key across a few popular CI/CD 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 the Telerik UI for WPF components at build time by using the provided license key.

If you cannot use NuGet packages in your project, you can add the license key as an assembly attribute as shown in the Installing License Key article.

The license activation process in a CI/CD environment involves the following steps:

1. Download a license key from your Telerik account.

2. Add the Telerik.Licensing NuGet package as a project dependency: <PackageReference Include="Telerik.Licensing" Version="1.*" />

3. Create an environment variable named TELERIK_LICENSE and add your UI for WPF 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)

1. Create a new User-defined Variable named TELERIK_LICENSE.

2. Paste the contents of the license key file as a value.

Azure Pipelines (Classic)

1. Create a new user-defined variable named TELERIK_LICENSE.

2. Paste the contents of the license key file as a value.

GitHub Actions

1. Create a new Repository Secret or an Organization Secret.

2. Set the name of the secret to TELERIK_LICENSE and paste the contents of the license file as a value.

3. After running npm install or yarn, add a build step to activate the license:

   [YML]

   env:
       TELERIK_LICENSE: $" }}