We are trying to activate the Kendo UI license as part of our CI/CD pipeline but are facing issues executing the npx kendo-ui-license activate command in our environment.
Environment Details:
We are using Microsoft OneBranch CI/CD pipeline templates.
Our NPM dependencies (including
@progresspackages) are hosted in a private Azure Artifacts registry.
Issue:
When we attempt to run the following command in the pipeline:
we receive the following error:
This appears to be due to the agent’s inability to establish a secure connection to the required endpoint(s), possibly related to Telerik's license validation server.
Request:
Could you please guide us on how to properly activate the Kendo UI license in a CI/CD environment that cannot execute the above command due to network restrictions?
Is there a supported method to pre-activate the license locally and provide the license file (e.g.,
.kendo-ui-license.json) in the pipeline instead?If so, could you confirm whether copying the license file to the appropriate location (e.g.,
~/.kendo-ui-license.json) is sufficient for the build to proceed without executing the activation command?
We would appreciate your assistance in identifying a secure and compliant way to use our licensed packages in our automated build process.
Thank you,
Milin Hapani
If your CI/CD system supports environment variables for secrets, you can also use the license key as an environment variable during the build:
https://www.telerik.com/kendo-react-ui/components/my-license/ci-services#github-actions
A build step must be added to activate the license after running npm install, as simply copying the license file to the correct location is not sufficient—it also needs to be activated during the build process.
Regards,
Filip