foreman source release pipeline failed:
https://ci.theforeman.org/job/foreman-develop-source-release/2271/
foreman source release pipeline failed:
https://ci.theforeman.org/job/foreman-develop-source-release/2271/
[2024-07-22T14:50:39.875Z] npm ERR! enoent Invalid response body while trying to fetch https://registry.npmjs.org/@babel%2fcore: ENOENT: no such file or directory, stat '/home/jenkins/.npm/_cacache/content-v2/sha512/d1/98/c80567efdca22591e3a300b44ceb76fb8c54d880683fb017d87dc2890e5d766ea67155e8e88cea078c9037e5d719f3f2d8b8442b7a419b5dbfea635475c0'
I think our npm cleaner script isn’t compatible with the newer NPM caching layout on EL9.
I wonder, do we really need it? Or can we rely on NPM not to be too stupid with its cache these days?
Reading npm-cache | npm Docs it seems it’s still “stupid” (“npm will not remove data by itself: the cache will grow as new packages are installed.”), but we rather should just call npm cache clean --force
every now and then instead of doing weird find
dances
I had the same train of thoughts. But at that point, is there a difference to simply removing ~/.npm
altogether? What if it happens during a CI run?
I guess “it depends”. As long as it’s not during the npm i
step, it should be fine, as the installed artifacts are in node_modules
? And yeah, if we’re not storing anything else in ~/.npm
, we can just yank that.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.