Why is my plugin showing up in the non-compatible applications list in the CDN Plugin health checks?

[Yingran Sun]

Why is my plugin showing up in the non-compatible applications list in the CDN Plugin health checks? How do I fix this?

[Yingran Sun · Accepted solution]

In Bitbucket Server 6.8, CDN support for caching static assets(such as JavaScript, CSS, and fonts) was added. This includes static resources that are served by plugins. The warning is displayed is when Bitbucket detects that a Marketplace or other user-installed app is using a deprecated method.

The following web-resource transforms and conditions have been deprecated:

• com.atlassian.plugin.webresource.transformer.WebResourceTransformer

• com.atlassian.plugin.web.Condition

If your plugin is making use of the APIs above, then it will appear on the non-compatible plugins list and may cause static assets to be cached incorrectly. You will need to update any incompatible apps, or contact the plugin vendor if an update is not yet available. For more information on how to move to the new web-resource APIs, see stateless web-resource transforms and conditions.