Skip dispatcher build in Cloud manager pipeline | Community
Skip to main content
June 9, 2022
Solved

Skip dispatcher build in Cloud manager pipeline

  • June 9, 2022
  • 1 reply
  • 1055 views

Hi,

 

I am developing an AEM project for the Adobe Brand Portal. Since we do not have a publisher instance I have removed the dispatcher module. But the cloud manager pipeline fails at the "Build & Unit Testing" stage. I see the following error in the build log. Is there a way to configure the pipeline to skip the dispatcher module?

 

 

End stage: Preconditions checking Begin stage: GIT_CLONE Got an SSH private key Cloning into '******************'... commitSha: ****************** End stage: GIT_CLONE Begin stage: CREATE_DISPATCHER_CONFIGURATION_ZIP ERROR: '44 CUSTOMER Opt-in file //opt-in/USE_SOURCES_DIRECTLY is not present. Build aborted.' at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) ERROR: Unexpected error type: 'CUSTOMER' at status.internal.errorStatus(/usr/local/bin/lib-status.bash:25) at status.error(/usr/local/bin/lib-status.bash:142) at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) ERROR: '1 TEST_FAILURE Cloning into '******************'... ERROR: '44 CUSTOMER Opt-in file //opt-in/USE_SOURCES_DIRECTLY is not present. Build aborted.' at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) ERROR: Unexpected error type: 'CUSTOMER' at status.internal.errorStatus(/usr/local/bin/lib-status.bash:25) at status.error(/usr/local/bin/lib-status.bash:142) at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211)' at reportError(/usr/local/bin/lib-status.bash:252) at status.error(/usr/local/bin/lib-status.bash:142) at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) Reporting error to: '/mnt/shared/status-build-zip' ERROR: '1 SCRIPT_ERROR Script command failed (see stack trace)' at status.internal.handleError(/usr/local/bin/lib-status.bash:51) at status.track(/usr/local/bin/lib-status.bash:266) at main(/usr/local/bin/build-zip.sh:211) Status file exists: '/mnt/shared/status-build-zip' assuming it is already saved in earlier step. Elapsed time: 3s Error: exited unexpectedly in stage 'build-zip' with status: 1 Touching shutdown file in case logging container waits for finish signal Listing customer artefact: Found unsuccessful status: /mnt/shared/status-build-zip Found unsuccessful status: /mnt/shared/status-validation Found unsuccessful status: /mnt/shared/status-backend-mock Found unsuccessful status: /mnt/shared/status-dispatcher generated build.json (converted to yaml) is: - phase: build url: git@ssh.dev.azure.com:v3/adobecloudmanager-****************** steps: - name: build succeeded: false artefacts: - path: build/ type: dispatcher-configuration logs: - path: build/dispatcher_build.log type: user-log exitCode: 1 errorCode: BUILD_WEB_TIER_BUILD_ZIP_TEST_FAILURE causedBy: CUSTOMER internalMessage: |- Cloning into '******************'... ERROR: '44 CUSTOMER Opt-in file //opt-in/USE_SOURCES_DIRECTLY is not present. Build aborted.' at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) ERROR: Unexpected error type: 'CUSTOMER' at status.internal.errorStatus(/usr/local/bin/lib-status.bash:25) at status.error(/usr/local/bin/lib-status.bash:142) at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) internalDetails: exitCode: 1 stackTrace: |2- at status.error(/usr/local/bin/lib-status.bash:142) at reportError(/usr/local/bin/lib-status.bash:252) at status.error(/usr/local/bin/lib-status.bash:142) at runBuild(/usr/local/bin/build-zip.sh:200) at status.track(/usr/local/bin/lib-status.bash:258) at main(/usr/local/bin/build-zip.sh:211) time: "2022-06-09T09:18:02Z" file: /mnt/shared/status-build-zip - name: codeQuality succeeded: false artefacts: [] logs: - path: build/dispatcher_validation.log type: user-log - path: build/dispatcher_runtime.log type: user-log - path: build/dispatcher_backend_mock.log type: user-log skipCodeQualityRules: true result: [] exitCode: 1 errorCode: BUILD_WEB_TIER_BUILD_ZIP_SCRIPT_ERROR causedBy: WEB_TIER_SERVICE internalMessage: 'Missing status file: [/mnt/shared/status-dispatcher].' internalDetails: exitCode: 1 stackTrace: |2- at status.read(/usr/local/bin/lib-status.bash:118) at updateBuildStatus(/usr/local/bin/build-zip.sh:55) at generateBuildJson(/usr/local/bin/build-zip.sh:81) at handleExit(/usr/local/bin/build-zip.sh:117) at status.internal.handleError(/usr/local/bin/lib-status.bash:1) at status.track(/usr/local/bin/lib-status.bash:266) at main(/usr/local/bin/build-zip.sh:211) time: "2022-06-09T09:18:03Z" file: /mnt/shared/status-dispatcher End stage: build-zip Begin stage: Publish logs appending additional logs to 'dispatcher_build.log': [ 'dispatcher_backend_mock.log dispatcher_validation.log' ]

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Himanshu_Jain

Keep dispatcher module and run the pipeline .

As your author instance is also serving via dispatcher only .

In cloud service you can have option to configure full stack , front-end and web tier config for pipeline only.

For more info refer : https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/overview/ci-cd-pipeline.html?lang=en


https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/cicd-pipelines/introduction-ci-cd-pipelines.html?lang=en

 

1 reply

Himanshu_Jain
Community Advisor
Himanshu_JainCommunity AdvisorAccepted solution
Community Advisor
June 9, 2022

Keep dispatcher module and run the pipeline .

As your author instance is also serving via dispatcher only .

In cloud service you can have option to configure full stack , front-end and web tier config for pipeline only.

For more info refer : https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/overview/ci-cd-pipeline.html?lang=en


https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/cicd-pipelines/introduction-ci-cd-pipelines.html?lang=en

 

Himanshu Jain