Many SAP Commerce projects are still using regular storefront approach, often incorporating modern frameworks like Vue.js and using default SAP Commerce build. Implementing parallel execution of FE and BE builds can lead to significant reductions in overall build time. Even for projects utilizing the OOTB Grunt build, parallelization can result in significant time savings. Furthermore, parallelization provides the valuable advantage of decoupling FE and BE builds, enabling developers to skip FE builds when focusing on BE development.
In some SAP Commerce setups, there is an unusual problem where web unit tests occasionally fail when run with a suppressed tenant. These tests encounter random failures while creating mock classes, resulting in exceptions like java.lang.NoClassDefFoundError: Could not initialize class org.mockito.codegen.
With Solr 8’s support ending in June 2024, it’s crucial for local environments to transition to Solr 9. Unlike cloud installations of SAP Commerce (where you can easily switch Solr versions via manifest.json), local setups encounter difficulties in switching between Solr versions.
In Java 11 was removed support of JAX-WS (JSR 224), and related classes like ant WsImport task, which are highly used in hybris installations for third-party SOAP integrations. For example, cybersource integration extension rely on both wsimport (generates cybersource client from wsdl during ant build) and JAX-WS to execute SOAP requests.
Usually it is extremely useful for QA and dev departments to identify build number on environment and verify that required code changes was really deployed. Unfortunately OOTB hybris doesn’t provide any mechanism for that.
Starting from January 15, 2020 maven central repository is not supporting access via http://repo1.maven.org/maven2 due to security reasons. Unfortunately under the hood hybris uses ant-maven-task, which is not maintained since 2011 and has hardcoded link to http version of maven central.
Adding any of SAP datahub integration extension in localextensions.xml leads to build error with root cause Extension doesn't specify a path and no scanned extension was matching the name.
OOTB hybris provides ant unittests command to run unit and integration tests, which are pretty low level and requires additional configuration to simplify run and result collection for DevOps. Below you can find configuration for buildcallbacks.xml, which you can just copy-paste into any hybris project (version 6.0+) and significantly simplify DevOps job required for setup of CI/CD pipeline.