Description:
馃憢 Team, we have recently added support for caching in GHES (target version 3.5). And we saw setup-java action is also using the Action cache service to cache dependency, based on user input, using the actions/cache package of actions/toolkit. Unlike other setup-* actions (like setup-node, setup-python), setup-java actions is not using any explicit condition for GHES (for example like in setup-python we have https://github.com/actions/setup-python/blob/main/src/setup-python.ts#L14-L16) . So for setup-java, no change is required to enable its cache usage on GHES but if you like to check the Action cache service presence before starting caching dependency you can add use this new isFeatureAvailable function present in @actions/toolkit 2.0.0 to check the presence of Actions cache service.
You can also refer to this change which we are doing for actions/cache action.
Please let me know if you need more clarification.
Description:
馃憢 Team, we have recently added support for caching in GHES (target version 3.5). And we saw
setup-javaaction is also using the Action cache service to cache dependency, based on user input, using theactions/cachepackage of actions/toolkit. Unlike other setup-* actions (like setup-node, setup-python), setup-java actions is not using any explicit condition for GHES (for example like in setup-python we have https://github.com/actions/setup-python/blob/main/src/setup-python.ts#L14-L16) . So for setup-java, no change is required to enable its cache usage on GHES but if you like to check the Action cache service presence before starting caching dependency you can add use this newisFeatureAvailablefunction present in@actions/toolkit 2.0.0to check the presence of Actions cache service.You can also refer to this change which we are doing for actions/cache action.
Please let me know if you need more clarification.