The Git branch associated with the pipeline cannot be found
- Error message: Invalid pipeline: XXXXXX. Reason=Branch=xxxx not found in repository.
- Cause: The Git branch the pipeline is configured to use has been deleted.
- Resolution: Re-create the missing Git branch using the exact same name, or re-configure the pipeline to build from a different, existing branch.
Build & Unit Testing
The Build and Unit Testing phase performs a Maven build (mvn clean package
) of the project checked out from the pipeline’s configured Git branch.
Errors identified in this phase should be re-producible building the project locally, with the following exceptions:
-
A maven dependency not available on Maven Central is used, and the Maven repository containing the dependency is either:
- Unreachable from Cloud Manager, such as a private internal Maven repository, or the Maven repository requires authentication and the incorrect credentials have been provided.
- Not explicitly registered in the project’s
pom.xml
. Note that, including Maven repositories is discouraged as it increases build times.
-
Unit tests fail due to timing issues. This may occur when unit tests are timing-sensitive. A strong indicator is relying on
.sleep(..)
in the test code. -
The use of unsupported Maven plugins.
Code Scanning
Code scanning performs static code analysis using a mix of Java and AEM-specific best practices.
Code scanning results in a build failure if a Critical Security vulnerabilities exist in the code. Lesser violations can be overridden, but it is recommended they are fixed. Note that code scanning is imperfect and can result in false positives.
To resolve code scanning issues, download the CSV-fomatted report provided by Cloud Manager via the Download Details button and review any entries.
For more details see AEM specific rules, see Cloud Manager documentations’ custom AEM-specific code scanning rules.
Build Images
Build image is responsible for combining the built code artifacts created in the Build & Unit Testing step with the AEM Release, to form a single deployable artifact.
While any code build and compilation issues are found during Build & Unit Testing, there may be configuration or structural issues identified when attempting to combine the custom build artifact with the AEM release.
Duplicate OSGi configurations
When multiple OSGi configurations resolve via runmode for the target AEM environment, the Build Image step fails with the error:
[ERROR] Unable to convert content-package [/tmp/packages/enduser.all-1.0-SNAPSHOT.zip]:
Configuration 'com.example.ExampleComponent' already defined in Feature Model 'com.example.groupId:example.all:slingosgifeature:xxxxx:X.X',
set the 'mergeConfigurations' flag to 'true' if you want to merge multiple configurations with same PID