cloud-mta-build-tool: Cloud MTA Build Tool gets stuck during "Neo" Build

We have been using “Cloud MTA Build Tool” as part of Jenkins Pipeline to build HTML5 applications for deployment to “Neo” and “Cloud Foundry”

In the past week we have suddenly experienced difficulties with “Cloud MTA Build Tool” building an HTML5 using UI5 builder for deployment to Neo (Multi-Target Archive Builder works)

mta.yaml + UI5.yml + package.json added at end

The build tool gets stuck on the step highlighted below, and does not continue:

Command in Jenkins job:

# execute MTA build mbt build -p=neo

14:56:04 [2020-02-21 14:56:04] INFO Cloud MTA Build Tool version 1.0.9 14:56:04 [2020-02-21 14:56:04] INFO generating the “Makefile_20200221145604.mta” file… 14:56:04 [2020-02-21 14:56:04] INFO done 14:56:04 [2020-02-21 14:56:04] INFO executing the “make -f Makefile_20200221145604.mta p=neo mtar= strict=true mode=” command… 14:56:04 [2020-02-21 14:56:04] INFO validating the MTA project 14:56:04 [2020-02-21 14:56:04] INFO validating the MTA project 14:56:04 [2020-02-21 14:56:04] INFO building the “devopsui5gbmhe3” module… 14:56:04 [2020-02-21 14:56:04] INFO executing the “npm install --production” command… 14:56:26 …npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 14:57:13 …npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. 14:57:27 … 14:57:27 > core-js@2.6.9 postinstall /var/lib/jenkins/workspace/DevOpsProject/Mike.Healey/neoexample/devops-devopsui5gbmhe3mta-push-build-free/src/node_modules/@ui5/cli/node_modules/core-js 14:57:27 > node scripts/postinstall || echo “ignore” 14:57:27 14:57:27 Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! 14:57:27 14:57:27 The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:  14:57:27 > https://opencollective.com/core-js  14:57:27 > https://www.patreon.com/zloirock  14:57:27 14:57:27 Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) 14:57:27 14:57:28 .npm notice created a lockfile as package-lock.json. You should commit this file. 14:57:28 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.7 (node_modules/@ui5/cli/node_modules/fsevents): 14:57:28 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.7: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”}) 14:57:28 14:57:28 added 691 packages from 718 contributors and audited 5207 packages in 78.745s 14:57:28 found 16 vulnerabilities (6 low, 10 moderate) 14:57:28 run npm audit fix to fix them, or npm audit for details 14:57:28 [2020-02-21 14:57:28] INFO the build results of the “devopsui5gbmhe3” module will be packed and saved in the “/var/lib/jenkins/workspace/DevOpsProject/Mike.Healey/neoexample/devops-devopsui5gbmhe3mta-push-build-free/src/.src_mta_build_tmp/devopsui5gbmhe3” folder

MTA.YAML

_schema-version: ‘2.1’ parameters: hcp-deployer-version: 1.1.0 ID: ui5gbmhe3mta version: 1.0.0 modules:

  • name: devopsui5gbmhe3 type: com.sap.hcp.html5 path: . parameters: version: ‘${timestamp}’ build-parameters: builder: npm

UI5.yaml

specVersion: ‘1.0’ metadata: name: devopsui5gbmhe3 type: application resources: configuration: propertiesFileSourceEncoding: UTF-8 builder: customTasks: - name: webide-extension-task-updateNeoApp afterTask: generateVersionInfo configuration: destDir: dist appFolder: webapp nameSpace: test - name: webide-extension-task-updateManifestJson afterTask: webide-extension-task-updateNeoApp configuration: appFolder: webapp destDir: dist - name: webide-extension-task-lint afterTask: webide-extension-task-updateManifestJson configuration: destDir: dist appFolder: webapp nameSpace: test - name: webide-extension-task-resources afterTask: webide-extension-task-lint configuration: nameSpace: test

package.json

{ “name”: “devopsui5gbmhe3”, “version”: “0.0.1”, “description”: “”, “private”: true, “devDependencies”: { “@ui5/cli”: “1.7.0”, “@sap/ui5-builder-webide-extension”: “1.0.9” }, “scripts”: { “build”: “ui5 build --a”, “test”: “uiveri5”, “linting”: “eslint .” }, “ui5”: { “dependencies”: [ “@sap/ui5-builder-webide-extension” ] } }

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (3 by maintainers)

Most upvoted comments

@ShimiT advised the following for the mta.yaml:

The path: . is not supported, in the way you can reclusively upload your project with an infinite loop especially on CI environment .change it and reference to the module, like webapp

but this contradicts SAP’s own advice CI/CD to SAP Fiori Development on SAP Cloud Platform

image

Although an MTAR is now generated following the adjustment and deploys to Neo subtenant, the application does not run and results in a white screen:

Just to remind you that the MTAR that was generated locally via Cloud MTA Build tool did deploy successfully to Neo. This implies that there is an issue when running same tool under Jenkin’s control.