Hi there,
We're currently using Github Actions for our CI/CD process along with remote caching via Nx Cloud (Replay) in our Nx monorepo. I've noticed that when we get a cache hit for our build task we end up with the invalid license watermark after deployment. No cache hits (or disabling remote caching) results in a deployment without the watermark. We currently have everything set up in the right order (npm ci --> activate license [via a secret] --> build --> deploy). Is there any way that the Kendo license activation can be applied successfully when our build process uses the cache? Thanks!
1 Answer, 1 is accepted
Hello Daniel,
I will paste the answer provided in the private support thread about the same topic.
Typically when a valid license is activated successfully, but the watermark and other invalid license attributes are still displayed, then this is related to some cache stored. We recommend in this case to delete the .angular folder along with node_modules and package-lock.json and do a clean npm install. After the packages are installed then activate the license with the command - npx kendo-ui-license activate.
https://www.telerik.com/kendo-angular-ui/components/licensing/faq#i-renewed-my-license-key-but-still-see-the-invalid-license-attributes-what-should-i-do
https://www.telerik.com/kendo-angular-ui/components/knowledge-base/license-troubleshooting-activation-warning-watermark/
Another approach that helps other customers is to perform some of the actions in a single step for example putting the angular cache clean, license activation, and angular build all into one step.
Regards,
Martin Bechev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Rank 1
Hi Martin,
Thank you for the response. Since this is a workflow being run via Github Actions, there is no .angular folder and node_modules is created fresh every time. Where the cache comes in is a third party tool we're using which caches our apps and libs in our Nx monorepo. Because we have a lot of apps and libs that dont change on every PR, we use caching to speed up our CI/CD pipeline. Is there any way to make the Kendo license activation play nice with a cache like this?
Hi Daniel,
Thank you for the provided details.
For this case, the license needs to be activated before the cache is created.
To store the activation in the cache, the license needs to be activated for each build.
Please try it out and let us know how it goes.