You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing the Powerpack S3 Remote cache, I came across this post which makes me wonder about the intended functionality of the remote cache. Is it supposed to work only in CI environments?
From early testing it seems that it neither pushes to or pulls from the remote cache when running tasks locally, which is not what I would have expected. There are no info or error messages displayed regarding caching (local cache still works as expected). There's also no information in the docs that I've been able to find regarding this.
Note: Caching works in our CI environment, so this doesn't seem to be a configuration issue?
Expected behaviour:
Remote cache will read/write regardless if task is run on developer machine or in CI environment.
If this isn't the intended behaviour, I would argue that the documentation needs to make it clear that that is the case.
The text was updated successfully, but these errors were encountered:
Documentation issue
Is there a specific documentation page you are reporting?
https://nx.dev/nx-enterprise/powerpack/custom-caching (Or somewhere adjacent)
Additional context or description
When implementing the Powerpack S3 Remote cache, I came across this post which makes me wonder about the intended functionality of the remote cache. Is it supposed to work only in CI environments?
From early testing it seems that it neither pushes to or pulls from the remote cache when running tasks locally, which is not what I would have expected. There are no info or error messages displayed regarding caching (local cache still works as expected). There's also no information in the docs that I've been able to find regarding this.
Note: Caching works in our CI environment, so this doesn't seem to be a configuration issue?
Expected behaviour:
Remote cache will read/write regardless if task is run on developer machine or in CI environment.
If this isn't the intended behaviour, I would argue that the documentation needs to make it clear that that is the case.
The text was updated successfully, but these errors were encountered: