on ‎2020 Jan 10 12:45 PM
Hi,
We didn't any build in cloud since last 23th Dec and since yesterday 9th Jan we're experiencing a build error that is a big stopper for us.
The error says that a custom extension is not in the project, but it is. and nobody changed anything inside the manifest.json
---------------------------------------------------------------
[ysetplatformproperties] Caused by: de.hybris.bootstrap.config.BootstrapConfigException: Extension 'customstorefront' doesn't specify a path and no scanned extension was matching the name. Please check file /opt/workspace/build/commerce-suite/hybris/config/localextensions.xml. [ysetplatformproperties] at de.hybris.bootstrap.config.PlatformConfig.createExtensionInfoFromXML(PlatformConfig.java:1413) [ysetplatformproperties] at de.hybris.bootstrap.config.PlatformConfig.readConfiguredExtensionsFromXMLFile(PlatformConfig.java:1230) [ysetplatformproperties] ... 32 more
BUILD FAILED /opt/workspace/build/commerce-suite/hybris/bin/platform/build.xml:16: The following error occurred while executing this line: /opt/workspace/build/commerce-suite/hybris/bin/platform/resources/ant/antmacros.xml:123: java.lang.RuntimeException: Error while evaluating file '/opt/workspace/build/commerce-suite/hybris/config/localextensions.xml'. Extension 'customstorefront' doesn't specify a path and no scanned extension was matching the name. Please check file /opt/workspace/build/commerce-suite/hybris/config/localextensions.xml.
Request clarification before answering.
Hi @ejf
I think there is some issue in repository structure as SAP Cloud build will be expecting in diff structure. Please check Update on Code Repository topics which is done recently by SAP. Also SAP has updated cloud version as well so check with documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue is with the changes in the requirement of the repository structure as noted in https://help.sap.com/viewer/1be46286b36a4aa48205be5a96240672/SHIP/en-US/063082e0485749629b7b5a612cc6.... In our case we ended up moving the custom extensions under the core-customize root folder and the cloud build process worked after that,
Hope that helps.
Thanks,
ganesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.