cancel
Showing results for 
Search instead for 
Did you mean: 

Project "Piper" does not build project

0 Kudos

Hello everyone,

we have a problem regarding a multi target application. When building the project in business application studio it runs perfectly fine. The node version in BAS is v16.16.0. The MBT version is 1.2.18.

For project piper we use the following files:

Jenkinsfile

@Library('piper-lib-os') _
node(){ stage('Prepare') { deleteDir() checkout scm setupCommonPipelineEnvironment script:this }
stage('Build') { mtaBuild script:this }}
### General project setup
general:
  inferBuildTool: true
### Step-specific configuration
steps:
  mtaBuild:
    buildTarget: 'CF'
    dockerImage: devxci/mbtci-java11-node16:1.2.16

The following error occurrs:

info mtaBuild - [2023-02-01 07:41:28] INFO building the "emoc_fe" module...

info mtaBuild - [2023-02-01 07:41:28] INFO executing the "npm install" command...

warn mtaBuild - npm WARN EBADENGINE Unsupported engine {

warn mtaBuild - npm WARN EBADENGINE package: '@sap/approuter@10.15.4',

warn mtaBuild - npm WARN EBADENGINE required: { node: '^12.0.0 || ^14.0.0' },

warn mtaBuild - npm WARN EBADENGINE current: { node: 'v16.15.0', npm: '8.5.5' }

warn mtaBuild - npm WARN EBADENGINE }

warn mtaBuild - npm WARN EBADENGINE Unsupported engine {

warn mtaBuild - npm WARN EBADENGINE package: 'http2@3.3.7',

warn mtaBuild - npm WARN EBADENGINE required: { node: '>=0.12.0 <9.0.0' },

warn mtaBuild - npm WARN EBADENGINE current: { node: 'v16.15.0', npm: '8.5.5' }

warn mtaBuild - npm WARN EBADENGINE }

warn mtaBuild - npm WARN EBADENGINE Unsupported engine {

warn mtaBuild - npm WARN EBADENGINE package: 'karma@1.7.1',

warn mtaBuild - npm WARN EBADENGINE required: { node: '0.10 || 0.12 || 4 || 5 || 6 || 7 || 8' },

warn mtaBuild - npm WARN EBADENGINE current: { node: 'v16.15.0', npm: '8.5.5' }

warn mtaBuild - npm WARN EBADENGINE }

warn mtaBuild - npm WARN deprecated har-validator@5.1.5: this library is no longer supported

warn mtaBuild - npm WARN deprecated scmp@1.0.0: scmp v2 uses improved core crypto comparison since Node v6.6.0

warn mtaBuild - npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

warn mtaBuild - npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

warn mtaBuild - npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated

warn mtaBuild - npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated

warn mtaBuild - npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated

warn mtaBuild - npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.

warn mtaBuild - npm WARN deprecated xmldom@0.1.27: Deprecated due to CVE-2021-21366 resolved in 0.5.0

warn mtaBuild - npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3

warn mtaBuild - npm WARN deprecated samsam@1.3.0: This package has been deprecated in favour of @sinonjs/samsam

warn mtaBuild - npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated

warn mtaBuild - npm WARN deprecated log4js@0.6.38: 0.x is no longer supported. Please upgrade to 6.x or higher.

warn mtaBuild - npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.

warn mtaBuild - npm WARN deprecated multiline@2.0.0: This was a fun hack, but now we have template literals, so use that instead.

warn mtaBuild - npm WARN deprecated http2@3.3.7: Use the built-in module in node 9.0.0 or newer, instead

warn mtaBuild - npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

warn mtaBuild - npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated

error mtaBuild - ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................[2023-02-01 07:51:28] ERROR could not execute the "npm install" command: the process was interrupted

error mtaBuild - [2023-02-01 07:51:28] ERROR could not build the "emoc_fe" module: the build timed out after 10m0s

info mtaBuild - make: *** [Makefile_20230201073720.mta:37: emoc_fe] Error 1

info mtaBuild - Error: could not build the MTA project: could not execute the "make -f Makefile_20230201073720.mta p=CF mtar=Emoc.mtar strict=true mode= t=\"/var/jenkins_home/workspace/emoc_jenkins_test\"" command: exit status 2

This is the package.json of the frontend module:

{ "name": "emoc_fe", "version": "0.0.1", "description": "", "main": "webapp/index.html", "keywords": [ "ui5", "openui5", "sapui5" ], "devDependencies": { "@sap/grunt-sapui5-bestpractice-build": "latest", "@sap/grunt-sapui5-bestpractice-test": "latest", "@sap/ui5-builder-webide-extension": "1.0.x", "@sap/ux-ui5-tooling": "1", "@ui5/cli": "^2.11.1", "@ui5/fs": "^2.0.6", "@ui5/logger": "^2.0.1", "mbt": "^1.0.15", "nodemon": "^2.0.15", "rimraf": "3.0.2", "ui5-task-zipper": "^0.3.1" }, "dependencies": { "@sap/approuter": "^10" }, "scripts": { "start": "node node_modules/@sap/approuter/approuter.js", "startmon": "nodemon node_modules/@sap/approuter/approuter.js", "start-local": "fiori run --open 'index.html'", "build": "ui5 build -a --clean-dest --include-task=generateManifestBundle generateCachebusterInfo", "deploy": "fiori verify", "deploy-config": "fiori add deploy-config", "unit-tests": "fiori run --open test/unit/unitTests.qunit.html", "int-tests": "fiori run --open test/integration/opaTests.qunit.html", "build:cf": "ui5 build preload --clean-dest --config ui5-deploy.yaml --include-task=generateManifestBundle generateCachebusterInfo" }, "ui5": { "dependencies": [ "@sap/ux-ui5-tooling", "@sap/ui5-builder-webide-extension", "ui5-task-zipper", "mbt" ] }}

Do you have any recommendations how to solve the error? The paackages do not seem to cause any error in BAS.

Thanks in advance.

Kind regards
Lukas

View Entire Topic
thorsten_duda
Explorer
0 Kudos

The first thing you could check, if the BAS runs the MTA build also in strict mode at the make call (strict=true).

0 Kudos

We did not specify a specific strict flag in BAS, so I assume we built it with strict=true, since this is the default.

I just tried both flags (strict=true and strict=false) and both builds worked in BAS.

thorsten_duda
Explorer
0 Kudos

I looked again in the log and I wondering about this error message:
[2023-02-01 07:51:28] ERROR could not execute the "npm install" command: the process was interrupted

error mtaBuild - [2023-02-01 07:51:28] ERROR could not build the "emoc_fe" module: the build timed out after 10m0s

Your CI build runs into a time out. I don't know your setup but it looks like a network/infrastructure issue.
The BAS has direct internet access.

0 Kudos

Thanks for that notice, but the git pull and the build of other modules before (database and backend services) run without any issues, so I assume network is not the problem.

I am a little confused regarding core-js:
warn mtaBuild - npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

That is used for karma, which is used for /@sap/grunt-sapui5-bestpractice-test

I tried to use the latest version of /@sap/grunt-sapui5-bestpractice-test but it still uses an outdated core-js version.

Do you have any recommendation how to continue?

Thanks in advance

thorsten_duda
Explorer
0 Kudos

I am not a UI5 expert but the grunt tools are outdated. I think it is worth to have a look here https://github.com/SAP/karma-ui5

0 Kudos

Ah thanks, we check on that.