mwinteringham
commented
2 years ago Hi @german-chacon it's been a while but are you able to provide the full build log so I can debug the issue?
Closed german-chacon closed 2 years ago
mwinteringham
commented
2 years ago Hi @german-chacon it's been a while but are you able to provide the full build log so I can debug the issue?
german-chacon
commented
2 years ago mwinteringham
commented
2 years ago Hi @german-chacon I only got a partial build log. Could you run the build again using the command build_locally.cmd > build.log
german-chacon
commented
2 years ago @mwinteringham here you go build.log
mwinteringham
commented
2 years ago Thanks for that @german-chacon it appears the frontend isn't building properly but the logs aren't showing why.
Could you go into the assets/js and run npm run build and send me the output.
german-chacon
commented
2 years ago @mwinteringham I just run it, but only got this:
λ npm run build
ui@1.5.0 build webpack --mode=production
'webpack' is not recognized as an internal or external command, operable program or batch file.
mwinteringham
commented
2 years ago @german-chacon try running npm install -g webpack then run it again and see what happens
german-chacon
commented
2 years ago @mwinteringham I run "npm install -g webpack" and then tried to build, but got the same issue
mwinteringham
commented
2 years ago I've just merged some updates to the build process, would you mind pulling down the changes and running again. Should give us a clearer failure message.
german-chacon
commented
2 years ago @mwinteringham here is the latest build log
mwinteringham
commented
2 years ago So it looks like npm install is failing when you build the frontend. Could you go into the assets/js folder and run npm install and see what the error is
german-chacon
commented
2 years ago @mwinteringham here is the log when running the command in assets/js 2022-11-05T05_27_36_013Z-debug-0.log
mwinteringham
commented
2 years ago Ok so this looks like an issue in terms of how your machine is configured. The error below shows that NodeJS is asking for the Desktop development with C++ add on of Visual Studio is installed. I must say that it's not an error I have come across, but it is not related to RBP:
1442 error gyp verb find VS msvs_version not set from command line or npm config 1442 error gyp verb find VS VCINSTALLDIR not set, not running in VS Command Prompt 1442 error gyp verb find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details 1442 error gyp verb find VS looking for Visual Studio 2015 1442 error gyp verb find VS - not found 1442 error gyp verb find VS not looking for VS2013 as it is only supported up to Node.js 8 1442 error gyp ERR! find VS 1442 error gyp ERR! find VS msvs_version not set from command line or npm config 1442 error gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt 1442 error gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details 1442 error gyp ERR! find VS looking for Visual Studio 2015 1442 error gyp ERR! find VS - not found 1442 error gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8 1442 error gyp ERR! find VS 1442 error gyp ERR! find VS ** 1442 error gyp ERR! find VS You need to install the latest version of Visual Studio 1442 error gyp ERR! find VS including the "Desktop development with C++" workload. 1442 error gyp ERR! find VS For more information consult the documentation at: 1442 error gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows 1442 error gyp ERR! find VS ** 1442 error gyp ERR! find VS
karunakaran1983
commented
2 years ago @german-chacon I faced the same issue which you faced and it got fixed when I uninstall and reinstall the versions given in Requirements part of Read.md. Please do check if this info helps to resolve your issue. Thanks
RBP is currently known to work with the following requirements:
JDK 15.0.2 or higher (Tested with JDK 18) Maven 3.6.3 Node 16.15.1 NPM 8.11.0
mwinteringham
commented
2 years ago I'm closing this issue as it's not related to RBP. But feel free to comment @german-chacon if you do run into more issues.
BenjaminOsei
commented
8 months ago Hi @german-chacon, have you managed to get the issue resolved? If so, could you share what worked for you?
I am trying to build in Windows 11 but I am getting the following:
[INFO] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for restful-booker-platform 1.5.SNAPSHOT: [INFO] [INFO] restful-booker-platform-auth ....................... SUCCESS [ 26.268 s] [INFO] restful-booker-platform-booking .................... SUCCESS [ 36.724 s] [INFO] restful-booker-platform-room ....................... SUCCESS [ 32.683 s] [INFO] restful-booker-platform-report ..................... SUCCESS [ 32.682 s] [INFO] restful-booker-platform-branding ................... SUCCESS [ 42.264 s] [INFO] restful-booker-platform-message .................... SUCCESS [ 50.656 s] [INFO] restful-booker-platform-assets ..................... FAILURE [ 24.975 s] [INFO] restful-booker-platform ............................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:06 min [INFO] Finished at: 2022-08-08T12:34:04+07:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on projectrestful-booker-platform-assets: There are test failures. [ERROR] [ERROR] Please refer to C:...\restful-booker-platform\assets\api\target\surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :restful-booker-platform-assets
when I check the surefire reports I see:
Test set: com.automationintesting.unit.taskanalysis.ServeContentTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 14.513 s <<< FAILURE! - in com.automationintesting.unit.taskanalysis.ServeContentTest checkUiServesStaticContent Time elapsed: 4.484 s <<< FAILURE! org.opentest4j.AssertionFailedError: expected: <
The application tries to start but it gets stuck:
####### RESTFUL-BOOKER-PLATFORM #######
STARTING APPLICATION...
#######################################
File Not Found Error: Unable to access jarfile assets/api/target/ Waiting for RBP to turn on....................................................... /auth/ ready .... /report/ ready .... /room/ ready . /booking/ ready /message/ ready /branding/ ready ................................................................................................../...
What could be the issue?