Closed sedouard closed 6 years ago
This is an interesting error. I haven't run into anything like this before, and I've been using Drone to build Node.js projects for a long time. Either way, it's super complex to clear cache based on a change set. Generally speaking Drone only checks out the head version for performance. This means this plugin does not have reliable access to the Git history.
These issues really shouldn't occur if you're just caching your node_modules folder. I think you'll have to look for the issue in your project setup.
I'm closing this because it's most likely a project setup issue.
I've been noticing NPM errors due to the cache restore like so:
I suspect this occurs after I make changes to
package.json
. Do you think it is feasible to trigger a cache clear if a certain file exists in the commit changeset that triggered the build?