Abhishek Pal created HDDS-13620:
-----------------------------------
Summary: Ozone builds are failing due to npm not being able to
access registry
Key: HDDS-13620
URL: https://issues.apache.org/jira/browse/HDDS-13620
Project: Apache Ozone
Issue Type: Bug
Reporter: Abhishek Pal
Assignee: Abhishek Pal
Current builds for Ozone is failing as npm is not able to access npmjs registry
{code:java}
[INFO] --- frontend:1.15.1:npx (set [email protected] store path) @ ozone-recon ---
[INFO] npm not inheriting proxy config from Maven
[INFO] Running 'npx [email protected] config set store-dir ~/.pnpm-store' in
/home/runner/work/ozone/ozone/hadoop-ozone/recon/src/main/resources/webapps/recon/ozone-recon-web
[INFO] npm WARN exec The following package was not found and will be installed:
[email protected]
[INFO] npm ERR! code E403
[INFO] npm ERR! 403 403 Forbidden - GET
https://registry.npmjs.org/pnpm/-/pnpm-8.15.7.tgz
[INFO] npm ERR! 403 In most cases, you or one of your dependencies are
requesting
[INFO] npm ERR! 403 a package version that is forbidden by your security
policy, or
[INFO] npm ERR! 403 on a server you do not have access to.
{code}
This needs to be fixed with either:
- Having pnpm installed/packaged directly on the image
- Setting npm registry to use http (might cause security issues)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
