AEM as cloud service | Python error on cloud build | Community
Skip to main content
New Participant
December 21, 2023
Solved

AEM as cloud service | Python error on cloud build

  • December 21, 2023
  • 3 replies
  • 921 views

Hello Team,

 

We are using AEM as CS for our project. We are some build issue on cloud environment as below. any guild will help us. thanks

 

 

 

6:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp info using node@14.17.3 | linux | x64
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python checking if "python3" can be used
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python checking if "python" can be used
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - "python" is not in PATH or produced an error
16:45:17,930 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python checking if "python2" can be used
16:45:17,931 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - "python2" is not in PATH or produced an error
16:45:17,932 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python
16:45:17,932 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python **********************************************************
16:45:17,933 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python You need to install the latest version of Python.
16:45:17,934 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
16:45:17,934 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python you can try one of the following options:
16:45:17,934 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
16:45:17,935 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python (accepted by both node-gyp and npm)
16:45:17,935 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - Set the environment variable PYTHON
16:45:17,935 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python - Set the npm configuration variable python:
16:45:17,935 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python For more information consult the documentation at:
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python **********************************************************
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! find Python
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! configure error
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
16:45:17,936 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at PythonFinder.fail (/build_root/build/qa/ui.frontend/node/node_modules/npm/node_modules/node-gyp/lib/find-python.js:302:47)
16:45:17,937 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at PythonFinder.runChecks (/build_root/build/qa/ui.frontend/node/node_modules/npm/node_modules/node-gyp/lib/find-python.js:136:21)
16:45:17,937 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/build_root/build/qa/ui.frontend/node/node_modules/npm/node_modules/node-gyp/lib/find-python.js:179:16)
16:45:17,937 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at PythonFinder.execFileCallback (/build_root/build/qa/ui.frontend/node/node_modules/npm/node_modules/node-gyp/lib/find-python.js:266:16)
16:45:17,937 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at exithandler (child_process.js:326:5)
16:45:17,938 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at ChildProcess.errorhandler (child_process.js:338:5)
16:45:17,938 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at ChildProcess.emit (events.js:375:28)
16:45:17,938 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
16:45:17,938 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at onErrorNT (internal/child_process.js:467:16)
16:45:17,938 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:82:21)
16:45:17,939 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! System Linux 5.10.102.2-microsoft-standard
16:45:17,939 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! command "/build_root/build/qa/ui.frontend/node/node" "/build_root/build/qa/ui.frontend/node/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
16:45:17,939 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! cwd /build_root/build/qa/ui.frontend/node_modules/node-expat
16:45:17,939 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! node -v v14.17.3
16:45:17,939 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! node-gyp -v v7.1.2
16:45:17,940 [Exec Stream Pumper] [INFO] npm ERR! gyp ERR! not ok
16:45:18,020 [Exec Stream Pumper] [INFO]
16:45:18,020 [Exec Stream Pumper] [INFO] npm ERR! A complete log of this run can be found in:
16:45:18,020 [Exec Stream Pumper] [INFO] npm ERR! /root/.npm/_logs/2023-12-21T16_45_17_977Z-debug.log
16:45:18,065 [main] [INFO] ------------------------------------------------------------------------

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

kautuk_sahni
Employee
January 3, 2024

@pradeepmoolemane Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
joerghoh
joerghohAccepted solution
Employee
December 22, 2023
New Participant
December 21, 2023

Hi Pradeep,

To resolve this issue you need to update the pom.xml file. Please follow the below article.

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-23141.html?lang=en

Regards,

Abhishek