SAP Community - SAP Continuous Integration and Delivery

CICD build failed

2023-11-22T02:23:58+01:00

Hi,

I was doing the CICD deployment and encountered an issue in running the CI/CD job. Below is the Log for the build failure. Deployement from BAS is working without any issues.

Stage Logs (risk-management-job #6 - Build)
[2023-11-22T00:52:10.725Z] [INFO] No runFirst command defined for current stage (Build). Will not execute additional commands step
[2023-11-22T00:52:11.267Z] Trying to acquire lock on [risk-management-job]
[2023-11-22T00:52:11.270Z] Resource [risk-management-job] did not exist. Created.
[2023-11-22T00:52:11.271Z] Lock acquired on [risk-management-job]
[2023-11-22T00:52:11.308Z] Running on Jenkins in /jenkins_home/workspace/risk-management-job@2
[2023-11-22T00:52:11.349Z] Unstash content: pipelineConfigAndTests
[2023-11-22T00:52:11.378Z] Unstash content: source
[2023-11-22T00:52:12.921Z] Unstash content: cloudcitransfer
[2023-11-22T00:52:12.985Z] [piperPipelineStageBuild] Sending telemetry data is disabled.
[2023-11-22T00:52:13.415Z] --- Begin library step of: buildExecute ---
[2023-11-22T00:52:13.642Z] [null] Sending telemetry data is disabled.
[2023-11-22T00:52:14.070Z] --- Begin library step of: mtaBuild ---
[2023-11-22T00:52:14.342Z] + '[' -x ./piper ]
[2023-11-22T00:52:14.353Z] Found piper binary in the workspace - skipping unstash
[2023-11-22T00:52:14.370Z] Unstash content: pipelineConfigAndTests
[2023-11-22T00:52:14.433Z] Step params [:]
[2023-11-22T00:52:14.477Z] PIPER_parametersJSON: {}
[2023-11-22T00:52:14.750Z] + ./piper getConfig --contextConfig --stepMetadata .pipeline/tmp/metadata/mtaBuild.yaml --defaultConfig .pipeline/.pipeline/cicdCustomDefaults.yml --ignoreCustomDefaults
[2023-11-22T00:52:14.751Z] time="2023-11-22T00:52:14Z" level=info msg="Version daf159ae1145d8c743bf54f673d6d8b7cecf0b9e" library=SAP/jenkins-library
[2023-11-22T00:52:14.751Z] time="2023-11-22T00:52:14Z" level=info msg="Printing stepName " library=SAP/jenkins-library
[2023-11-22T00:52:14.781Z] Context Config: [dockerImage:devxci/mbtci-java17-node18@sha256:3c4903882815c3a2a67bfb30b3842ad90d85ee10da4224a7b39a5a0dd1a3e21f, dockerPullImage:false]
[2023-11-22T00:52:14.800Z] [INFO] executing pipeline step 'mtaBuild' with docker image 'devxci/mbtci-java17-node18@sha256:3c4903882815c3a2a67bfb30b3842ad90d85ee10da4224a7b39a5a0dd1a3e21f'
[2023-11-22T00:52:15.384Z] --- Begin library step of: dockerExecute ---
[2023-11-22T00:52:15.596Z] [dockerExecute] Sending telemetry data is disabled.
[2023-11-22T00:52:16.204Z] --- Begin library step of: dockerExecuteOnKubernetes ---
[2023-11-22T00:52:16.410Z] [dockerExecuteOnKubernetes] Sending telemetry data is disabled.
[2023-11-22T00:52:16.429Z] Stash content: workspace-e48a1485-28ed-42a6-a19d-ce0ec1205776 (includes: **/*, excludes: nohup.out, useDefaultExcludes: true, allowEmpty: true)
[2023-11-22T00:52:24.773Z] Stashed 65 file(s)
[2023-11-22T00:52:28.018Z] Created Pod: kubernetes steward-run-2tmrp-main-6rjd4/dynamic-agent-e48a1485-28ed-42a6-a19d-ce0ec1205776-0rkc4-ks2sz
[2023-11-22T00:52:31.055Z] Agent dynamic-agent-e48a1485-28ed-42a6-a19d-ce0ec1205776-0rkc4-ks2sz is provisioned from template dynamic-agent-e48a1485-28ed-42a6-a19d-ce0ec1205776-0rkc4
[2023-11-22T00:52:31.261Z] Running on dynamic-agent-e48a1485-28ed-42a6-a19d-ce0ec1205776-0rkc4-ks2sz in /home/jenkins/agent/workspace/risk-management-job
[2023-11-22T00:52:31.465Z] ContainerConfig: [name:container-exec]
[2023-11-22T00:52:31.500Z] Unstash content: workspace-e48a1485-28ed-42a6-a19d-ce0ec1205776
[2023-11-22T00:52:34.537Z] invalidate stash workspace-e48a1485-28ed-42a6-a19d-ce0ec1205776
[2023-11-22T00:52:34.556Z] Stash content: workspace-e48a1485-28ed-42a6-a19d-ce0ec1205776 (includes: **/*.*, excludes: **/*, useDefaultExcludes: true, allowEmpty: true)
[2023-11-22T00:52:34.575Z] Warning: overwriting stash ‘workspace-e48a1485-28ed-42a6-a19d-ce0ec1205776’
[2023-11-22T00:52:34.707Z] Stashed 0 file(s)
[2023-11-22T00:52:34.719Z] [INFO][dockerExecute] Executing inside a Kubernetes Pod
[2023-11-22T00:52:35.476Z] + ./piper writePipelineEnv
[2023-11-22T00:52:35.476Z] time="2023-11-22T00:52:35Z" level=info msg="Version daf159ae1145d8c743bf54f673d6d8b7cecf0b9e" library=SAP/jenkins-library
[2023-11-22T00:52:35.541Z] Unstash content: pipelineStepReports
[2023-11-22T00:52:35.571Z] Unstash failed: pipelineStepReports (No such saved stash ‘pipelineStepReports’)
[2023-11-22T00:52:36.230Z] + ./piper mtaBuild --defaultConfig .pipeline/.pipeline/cicdCustomDefaults.yml --ignoreCustomDefaults
[2023-11-22T00:52:36.231Z] time="2023-11-22T00:52:36Z" level=info msg="Version daf159ae1145d8c743bf54f673d6d8b7cecf0b9e" library=SAP/jenkins-library
[2023-11-22T00:52:36.231Z] info  mtaBuild - running command: npm config get registry
[2023-11-22T00:52:36.497Z] info  mtaBuild - Discovered pre-configured npm registry registry with value https://registry.npmjs.com/
[2023-11-22T00:52:36.497Z] 
[2023-11-22T00:52:36.498Z] info  mtaBuild - "mta.yaml" file found in project sources
[2023-11-22T00:52:36.498Z] info  mtaBuild - No timestamp contained in "mta.yaml". File has not been modified.
[2023-11-22T00:52:36.498Z] info  mtaBuild - Executing mta build call: "mbt build --mtar risk-management.mtar --platform CF --source ./ --target /home/jenkins/agent/workspace/risk-management-job"
[2023-11-22T00:52:36.498Z] info  mtaBuild - running command: mbt build --mtar risk-management.mtar --platform CF --source ./ --target /home/jenkins/agent/workspace/risk-management-job
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO Cloud MTA Build Tool version 1.2.25
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO generating the "Makefile_20231122005236.mta" file...
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO done
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO executing the "make -f Makefile_20231122005236.mta p=CF mtar=risk-management.mtar strict=true mode= t=\"/home/jenkins/agent/workspace/risk-management-job\"" command...
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO validating the MTA project
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO running the "before-all" build...
[2023-11-22T00:52:36.498Z] info  mtaBuild - [2023-11-22 00:52:36]  INFO executing the "npx cds build --production" command...
[2023-11-22T00:52:37.434Z] error mtaBuild - npm ERR! could not determine executable to run
[2023-11-22T00:52:37.434Z] info  mtaBuild - 
[2023-11-22T00:52:37.434Z] error mtaBuild - npm ERR! A complete log of this run can be found in:
[2023-11-22T00:52:37.434Z] error mtaBuild - npm ERR!     /home/mta/.npm/_logs/2023-11-22T00_52_36_822Z-debug-0.log
[2023-11-22T00:52:37.434Z] error mtaBuild - [2023-11-22 00:52:37] ERROR the "before-all"" build failed: could not execute the "npx cds build --production" command: exit status 1
[2023-11-22T00:52:37.434Z] info  mtaBuild - make: *** [Makefile_20231122005236.mta:28: pre_build] Error 1
[2023-11-22T00:52:37.434Z] info  mtaBuild - Error: could not build the MTA project: could not execute the "make -f Makefile_20231122005236.mta p=CF mtar=risk-management.mtar strict=true mode= t=\"/home/jenkins/agent/workspace/risk-management-job\"" command: exit status 2
[2023-11-22T00:52:37.434Z] info  mtaBuild - fatal error: errorDetails{"category":"build","correlationId":"n/a","error":"running command 'mbt' failed: cmd.Run() failed: exit status 1","library":"SAP/jenkins-library","message":"failed to execute mta build","result":"failure","stepName":"mtaBuild","time":"2023-11-22T00:52:37.361631795Z"}
[2023-11-22T00:52:37.434Z] fatal mtaBuild - failed to execute mta build - running command 'mbt' failed: cmd.Run() failed: exit status 1
[2023-11-22T00:52:37.434Z] info  mtaBuild - persisting reports to GCS is disabled, because gcsBucketId is empty
[2023-11-22T00:52:37.435Z] info  mtaBuild - Step telemetry data:{"StepStartTime":"2023-11-22 00:52:36.04385709 +0000 UTC","PipelineURLHash":"50f013532a9770a2c2cfdc38b7581dd01df69b70","BuildURLHash":"50f013532a9770a2c2cfdc38b7581dd01df69b70","StageName":"Build","StepName":"mtaBuild","ErrorCode":"1","StepDuration":"1318","ErrorCategory":"build","CorrelationID":"n/a","PiperCommitHash":"daf159ae1145d8c743bf54f673d6d8b7cecf0b9e","ErrorDetail":{"category":"build","correlationId":"n/a","error":"running command 'mbt' failed: cmd.Run() failed: exit status 1","library":"SAP/jenkins-library","message":"failed to execute mta build","result":"failure","stepName":"mtaBuild","time":"2023-11-22T00:52:37.361631795Z"}}
[2023-11-22T00:52:38.199Z] + ./piper readPipelineEnv
[2023-11-22T00:52:38.199Z] time="2023-11-22T00:52:37Z" level=info msg="Version daf159ae1145d8c743bf54f673d6d8b7cecf0b9e" library=SAP/jenkins-library
[2023-11-22T00:52:38.238Z] Transfer Influx data
[2023-11-22T00:52:38.273Z] Stash content: pipelineStepReports (includes: .pipeline/stepReports/**, excludes: , useDefaultExcludes: true, allowEmpty: true)
[2023-11-22T00:52:38.296Z] Stashed 0 file(s)
[2023-11-22T00:52:39.051Z] Stash content: container-e48a1485-28ed-42a6-a19d-ce0ec1205776 (includes: **/*, excludes: **/node_modules/**,nohup.out, useDefaultExcludes: true, allowEmpty: true)
[2023-11-22T00:52:47.190Z] Stashed 73 file(s)
[2023-11-22T00:52:47.313Z] Unstash content: container-e48a1485-28ed-42a6-a19d-ce0ec1205776
[2023-11-22T00:52:49.422Z] invalidate stash container-e48a1485-28ed-42a6-a19d-ce0ec1205776
[2023-11-22T00:52:49.440Z] Stash content: container-e48a1485-28ed-42a6-a19d-ce0ec1205776 (includes: **/*.*, excludes: **/*, useDefaultExcludes: true, allowEmpty: true)
[2023-11-22T00:52:49.462Z] Warning: overwriting stash ‘container-e48a1485-28ed-42a6-a19d-ce0ec1205776’
[2023-11-22T00:52:49.470Z] Stashed 0 file(s)
[2023-11-22T00:52:49.546Z] ----------------------------------------------------------
[2023-11-22T00:52:49.547Z] --- An error occurred in the library step: dockerExecuteOnKubernetes
[2023-11-22T00:52:49.547Z] ----------------------------------------------------------
[2023-11-22T00:52:49.547Z] 
[2023-11-22T00:52:49.547Z] The following parameters were available to the step:
[2023-11-22T00:52:49.547Z] ***
[2023-11-22T00:52:49.547Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2023-11-22T00:52:49.547Z] *** WARNING: this may reveal sensitive information. ***
[2023-11-22T00:52:49.547Z] ***
[2023-11-22T00:52:49.547Z] 
[2023-11-22T00:52:49.547Z] The error was:
[2023-11-22T00:52:49.547Z] ***
[2023-11-22T00:52:49.547Z] hudson.AbortException: [mtaBuild] Step execution failed (category: build). Error: running command 'mbt' failed: cmd.Run() failed: exit status 1
[2023-11-22T00:52:49.547Z] ***
[2023-11-22T00:52:49.547Z] 
[2023-11-22T00:52:49.547Z] Further information:
[2023-11-22T00:52:49.547Z] * Documentation of library step dockerExecuteOnKubernetes: https://sap.github.io/jenkins-library/steps/dockerExecuteOnKubernetes/
[2023-11-22T00:52:49.547Z] * Source code of library step dockerExecuteOnKubernetes: https://github.com/SAP/jenkins-library/blob/master/vars/dockerExecuteOnKubernetes.groovy
[2023-11-22T00:52:49.547Z] * Library documentation: https://sap.github.io/jenkins-library/
[2023-11-22T00:52:49.547Z] * Library repository: https://github.com/SAP/jenkins-library/
[2023-11-22T00:52:49.547Z] 
[2023-11-22T00:52:49.547Z] ----------------------------------------------------------
[2023-11-22T00:52:49.547Z] --- End library step of: dockerExecuteOnKubernetes ---
[2023-11-22T00:52:49.595Z] ----------------------------------------------------------
[2023-11-22T00:52:49.595Z] --- An error occurred in the library step: dockerExecute
[2023-11-22T00:52:49.595Z] ----------------------------------------------------------
[2023-11-22T00:52:49.595Z] 
[2023-11-22T00:52:49.596Z] The following parameters were available to the step:
[2023-11-22T00:52:49.596Z] ***
[2023-11-22T00:52:49.596Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2023-11-22T00:52:49.596Z] *** WARNING: this may reveal sensitive information. ***
[2023-11-22T00:52:49.596Z] ***
[2023-11-22T00:52:49.596Z] 
[2023-11-22T00:52:49.596Z] The error was:
[2023-11-22T00:52:49.596Z] ***
[2023-11-22T00:52:49.596Z] hudson.AbortException: [mtaBuild] Step execution failed (category: build). Error: running command 'mbt' failed: cmd.Run() failed: exit status 1
[2023-11-22T00:52:49.596Z] ***
[2023-11-22T00:52:49.596Z] 
[2023-11-22T00:52:49.596Z] Further information:
[2023-11-22T00:52:49.596Z] * Documentation of library step dockerExecute: https://sap.github.io/jenkins-library/steps/dockerExecute/
[2023-11-22T00:52:49.596Z] * Source code of library step dockerExecute: https://github.com/SAP/jenkins-library/blob/master/vars/dockerExecute.groovy
[2023-11-22T00:52:49.596Z] * Library documentation: https://sap.github.io/jenkins-library/
[2023-11-22T00:52:49.596Z] * Library repository: https://github.com/SAP/jenkins-library/
[2023-11-22T00:52:49.596Z] 
[2023-11-22T00:52:49.596Z] ----------------------------------------------------------
[2023-11-22T00:52:49.596Z] --- End library step of: dockerExecute ---
[2023-11-22T00:52:49.671Z] ----------------------------------------------------------
[2023-11-22T00:52:49.671Z] --- An error occurred in the library step: mtaBuild
[2023-11-22T00:52:49.671Z] ----------------------------------------------------------
[2023-11-22T00:52:49.671Z] 
[2023-11-22T00:52:49.671Z] The following parameters were available to the step:
[2023-11-22T00:52:49.671Z] ***
[2023-11-22T00:52:49.671Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2023-11-22T00:52:49.671Z] *** WARNING: this may reveal sensitive information. ***
[2023-11-22T00:52:49.671Z] ***
[2023-11-22T00:52:49.671Z] 
[2023-11-22T00:52:49.671Z] The error was:
[2023-11-22T00:52:49.671Z] ***
[2023-11-22T00:52:49.671Z] hudson.AbortException: [mtaBuild] Step execution failed (category: build). Error: running command 'mbt' failed: cmd.Run() failed: exit status 1
[2023-11-22T00:52:49.672Z] ***
[2023-11-22T00:52:49.672Z] 
[2023-11-22T00:52:49.672Z] Further information:
[2023-11-22T00:52:49.672Z] * Documentation of library step mtaBuild: https://sap.github.io/jenkins-library/steps/mtaBuild/
[2023-11-22T00:52:49.672Z] * Source code of library step mtaBuild: https://github.com/SAP/jenkins-library/blob/master/vars/mtaBuild.groovy
[2023-11-22T00:52:49.672Z] * Library documentation: https://sap.github.io/jenkins-library/
[2023-11-22T00:52:49.672Z] * Library repository: https://github.com/SAP/jenkins-library/
[2023-11-22T00:52:49.672Z] 
[2023-11-22T00:52:49.672Z] ----------------------------------------------------------
[2023-11-22T00:52:49.672Z] --- End library step of: mtaBuild ---
[2023-11-22T00:52:49.714Z] ----------------------------------------------------------
[2023-11-22T00:52:49.714Z] --- An error occurred in the library step: buildExecute
[2023-11-22T00:52:49.714Z] ----------------------------------------------------------
[2023-11-22T00:52:49.714Z] 
[2023-11-22T00:52:49.714Z] The following parameters were available to the step:
[2023-11-22T00:52:49.714Z] ***
[2023-11-22T00:52:49.714Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2023-11-22T00:52:49.714Z] *** WARNING: this may reveal sensitive information. ***
[2023-11-22T00:52:49.714Z] ***
[2023-11-22T00:52:49.715Z] 
[2023-11-22T00:52:49.715Z] The error was:
[2023-11-22T00:52:49.715Z] ***
[2023-11-22T00:52:49.715Z] hudson.AbortException: [mtaBuild] Step execution failed (category: build). Error: running command 'mbt' failed: cmd.Run() failed: exit status 1
[2023-11-22T00:52:49.715Z] ***
[2023-11-22T00:52:49.715Z] 
[2023-11-22T00:52:49.715Z] Further information:
[2023-11-22T00:52:49.715Z] * Documentation of library step buildExecute: https://sap.github.io/jenkins-library/steps/buildExecute/
[2023-11-22T00:52:49.715Z] * Source code of library step buildExecute: https://github.com/SAP/jenkins-library/blob/master/vars/buildExecute.groovy
[2023-11-22T00:52:49.715Z] * Library documentation: https://sap.github.io/jenkins-library/
[2023-11-22T00:52:49.715Z] * Library repository: https://github.com/SAP/jenkins-library/
[2023-11-22T00:52:49.715Z] 
[2023-11-22T00:52:49.715Z] ----------------------------------------------------------
[2023-11-22T00:52:49.715Z] --- End library step of: buildExecute ---
[2023-11-22T00:52:49.734Z] Stash content: cloudcitransfer (includes: cloudcitransfer/**/*, excludes: cloudcitransfer/**/node_modules/**)
[2023-11-22T00:52:49.765Z] Warning: overwriting stash ‘cloudcitransfer’
[2023-11-22T00:52:49.766Z] Stashed 2 file(s)
[2023-11-22T00:52:49.836Z] [null] Sending telemetry data is disabled.
[2023-11-22T00:52:49.880Z] Lock released on resource [risk-management-job]

Regards,

Jono Thomas

SAP BTP CI/CD fail in Additional Test - Error: running command 'npm' failed

2023-11-27T03:52:03+01:00

Hi there,

When running CI/CD for my test CAP Build, I'm getting the following error:

[2023-11-27T02:41:38.133Z] ----------------------------------------------------------
[2023-11-27T02:41:38.133Z] --- An error occurred in the library step: dockerExecute
[2023-11-27T02:41:38.133Z] ----------------------------------------------------------
[2023-11-27T02:41:38.133Z] 
[2023-11-27T02:41:38.133Z] The following parameters were available to the step:
[2023-11-27T02:41:38.133Z] ***
[2023-11-27T02:41:38.133Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2023-11-27T02:41:38.133Z] *** WARNING: this may reveal sensitive information. ***
[2023-11-27T02:41:38.133Z] ***
[2023-11-27T02:41:38.133Z] 
[2023-11-27T02:41:38.133Z] The error was:
[2023-11-27T02:41:38.133Z] ***
[2023-11-27T02:41:38.133Z] hudson.AbortException: [npmExecuteScripts] Step execution failed (category: build). Error: running command 'npm' failed: cmd.Run() failed: exit status 1
[2023-11-27T02:41:38.133Z] ***
[2023-11-27T02:41:38.133Z] <br>

Relevant mta.yaml npm build as follows:

Manually running "npm run test" in VSCode it's all good.

Not sure where it went wrong? Any help appreciated thanks!

CI/CD with ABAP Environment

2023-12-06T11:27:48+01:00

Hello everyone,

I have completed the following two tutorials:

Then I have deployed the app in my dev subaccount and integrated it into SAP Build Work Zone.

I would now like to use CI/CD to automatically deploy my entire application (frontend and backend) to the dev subaccount during commit/push and make it available for import in the test subaccount.

What would be the best practice approach for this scenario?

How to Deploy a Fiori app on on-premise server using BTP CICD service's Source Repo?

2024-01-04T07:18:51+01:00

Hi All,
Here I am using BTP CICD, GitHub webhook and BAS for the entire application deployment.

1. Here is the Job Status: the Release Stage is failed. Here I am using Source Repository as Stage.

2. Error log is:

3. config.yaml

4. Project Structure:

5. Credential List:

I have added all the things as per

https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-delivery/configure-sap-fiori-for-abap-platform-job-in-your-repository#loioa859560bca4149488f8e94e9c9a9adad

but Still I m getting error as mention in the error log ,Cannot get property 'uploadCredentialsId' on null object

as I declared in the config file but still getting this error, can anyone help me out whats the solution?

CICD Release failed on BTP trial account.

2024-01-04T12:38:53+01:00

Hi Team,

We are getting the attached error while running the cicd job to deploy application through cloud transport management system in BTP trial account.

Please assist.deploy-error.txt

Regards,

Dwipin

Trigger CI/CD Build on Merge

2024-01-04T16:26:38+01:00

As it is best practice to not directly push code onto the main Branch, I'd like to only build on a successful merge, and thus exclude any accidental non-merge push events from triggering a build. Just to be safe.
But while setting up a webhook between Azure DevOps and the CI/CD Service I noticed that so far only the "Code Push" event seems to be supported. With all other event types returning 400 Bad Request.

Response with Push:

Response with Merge:

While "Code Push" works fine most of the time. The additional granularity would be welcome.
Is there any chance that we could get support for more event types?

VA02 Requested Delivery date Arrival Time is late in the day

2024-02-12T16:57:05.714000+01:00

While in VA02, I was updating requested delivery dates, and while in the date field of the pop-up box, I hit F7, and received a warning message stating "Goods accepted from 03:00 to and from to 21:59". I can click through this warning message, however I noticed that the arrival time on that pop-up box is now 23:02:00 or a similar timeframe, whereas it should be something more like 08:03:00. I'm trying to figure out how to have that time to auto-populate correctly again, and how pressing F7 may have messed it up.

To implement CICD Pipeine for Fiori Projects

2024-02-14T10:43:22.745000+01:00

Hi, I want to implement CICD Pipeline for Fiori Freestyle projects

I have followed the tutorials i am able to connect with GitHub and CICD and even webhook is triggered.

The Github is failing because recently we have with extra security when we push the code from BAS to Github to main it will generate OTP for access the repository. due to this step its failing.

Do anyone has the similar issue or if you have implemented can you help me?

different calendar for the same shipping point

2024-02-21T03:05:33.775000+01:00

Hi all,

Can we create different calendar for LCL and FCL shipment with the same shipping point or we must use different shipping point for FCL and LCL?

Customer of FCL and LCL are different.

Thanks!

SAP BAS - CI/CD Builds: No option to Create a Job

2024-02-27T05:59:28.032000+01:00

Hi all,

Following a tutorial, it looks like this button should be available in SAP BAS:

But mine just shows this, none of the buttons seem to help. Any ideas on what's going wrong?

Thanks!

Crystal report CI/CD on azure app service

2024-02-29T20:05:49.347000+01:00

Our team decided to implement CI/CD on Azure app services with the existing system(asp .net c#) implemented by Crystal Report. We did some research and found different answers but it seems that the Azure platform is not currently supported.
This blog suggested a way but most of the comments show that it doesn't work for most developers and they were faced with multiple blockages and errors.

We want to be sure about it so that we can think about the replacement with confidence otherwise. Are there any recommendations and possible solutions?

CICD - Configure an SAP Fiori for the onpremise ABAP Platform

2024-03-04T16:05:22.662000+01:00

Hi All,

I am new and trying to build the pipeline using CICD services for Freestyle Fiori projects. i have to deploy the app to the on premise ABAP platform using CICD. Currently the infrastructure works fine for manual deployment.

Currently i have created the job in CICD and able to complete the prerequisite steps like job creation, credentials mapping, web hook. init and build stage is successful. i need your help for setting up release stage

Configure the stages of your SAP Fiori for the ABAP platform job directly in the SAP Continuous Integration and Delivery service.

In the release stage - Upload Credentials - is the gateway server credentials to be given?

Configure the stages of your SAP Fiori for the ABAP platform job in your repository.

In the Git repository in which your project sources reside, create a new file named .pipeline/config.yml.
Copy the following content into your config.yml file:

these steps do anyone has the sample file with all the configuration steps written

Regards,

Ragavie

Specific doubt - Is there any transation for this?

2024-03-08T15:29:50.329000+01:00

Hello!!

I would like to know if there is any transaction that allows me to know the orders that were left behind.
I will try to be as specific as possible.

Let's see something real:

My company has a 48-hour limit to deliver orders to the customer, that is, I place an order on February 12th, the expected delivery date is February 14th.
The system then issues an order to the warehouse for the warehouse to organize the order and place it for picking so that the carrier can pick it up and deliver it on the following day (February 13th) by February 14th, as defined.

But for some reason, there is a product that was supposed to be in stock on the defined days and is not, due to a delay in supply.
So when the system automatically sends it to the warehouse, this product is not mentioned and does not go on the delivery note for picking and then transportation.

The question is: How can I anticipate a failure on a delivery to the customer and notify the customer in advance?
Is there any way to see why or how the system itself did not send the product to the warehouse in advance? Any transaction? Or multiple transactions? Maybe I can export some files and make an excel and determinate something?

Please, I really need your help. My job depends on this. Any help would be amazing! I hope I was enlightening and that you understand my doubts. I'm not native English.

Thank you so much!!!

During VL02N PGI, get error "Change the inspection stock of Material in QM only"

2024-03-10T22:52:50.083000+01:00

Hi Experts,

As per scenario, "Sample consumption" of 5 qty posted from QM through QA11 (Only stock posting performed). Since Storage location of Inspection lot is integrated with decentralized WH, Outbound delivery is triggered after QA11 sample posting. The Movement type inside this Outbound delivery is 331, but stock type is "Blank".

We did the following and got same error both cases,

Tried to post PGI with stock type blank, we got below error
Updated delivery stock type value "X - Quality" using Inbound IDOC from decentralized WH and tried PGI. Still we get same error.

ERROR - Change the inspection stock of Material in QM only.

Business couldn't do PGI. Is there any alternate way? Kindly help on the above.

Regards,

Jeffrey

Continuous Integration and Delivery Failed to load pipeline definitions

2024-03-29T14:10:27.857000+01:00

I have this issue even tho I added my user to CICD Service Developer and CICD Service Administrator

CI/CD Credentials - Stage: release error

2024-04-09T11:12:53.165000+02:00

Hi community!
I am trying to connect my CI/CD to my github, which is also connected to my BAS. Once I push a change in BAS, I want the all of the stages to be automated in CI/CD, but im having an issue from the logs, related to some credentials or authorization. Note that every stage, except the release stage is successful. In my config.yml file I have specified: cfCredentialsId: "deploy-to-cf", which I have used as a credential name in CI/CD, using basic authorization, where I am using my login details as email/password (is this wrong?). FYI, I am logged into Cloud foundry on BAS, but the way I logged into cloud foundry that way was by using a SSO Passcode, and not email/pw, so maybe I need to change the AUTH type in ci/cd to something else?
Thanks in advance for all help 🙂

Authentication for e2e Test Automation on BTP with SAP CI/CD, wdi5 and BTP Build & Workzone

2024-04-11T16:11:30.780000+02:00

Dear fellow people interested in test automation on btp

I face the problem of authentication on SAP Build & Workzone service in order for being able to execute automated tests from our SAP CI/CD Pipeline. The reason of this is, that I don't know how to authenticate via SAP Universal ID automatically in a pipeline environment. But let's give you a broad overview first.

We are developing applications in CAP for the cloud foundry environment. Those applications are build, tested and deployed in pipelines in the SAP CI/CD service.
The html5 applications are collected and displayed in SAP Build & Workzone, so POs and Devs can do all necessary tests for new features.
In my opinion, it does make sense to also do the e2e tests over Build & Workzone, so that we have a single point for all testing. We do the e2e tests with webdriver.io and the wdi5 plugin, which does work super well on a local instance.

The problem is now, that I don't know how to automatically log in from the pipeline into build & workzone in order to have the proper permission to access the applications. I already tried to automate the login with SAP Universal ID. The problem is there, that after several logins a captcha appears, which is not solvable automatically (of course this is intended).

So what is the proper way to set up this kind of authentication ?
Is a private authentication provider necessary for this kind of setup ?
Is the setup just wrong and there is another, maybe more elegant way to do this ?

I am happy for any kind of input and suggestions. If something should be unclear please ask 🙂

cheers

David

Issues faced in the Building Side-by-Side Extensions on SAP BTP

2024-04-25T08:33:00.862000+02:00

Hi All,

I have implemented the Side by Side Extension on SAP BTP using CAP (https://learning.sap.com/learning-journeys/build-side-by-side-extensions-on-sap-btp) and I am currently facing 3 issues as follows:
1. When I run my Risk Management App locally, I get the below error:

I would like to know which Auth aspect would I need to check to resolve this. This was working fine before but have started to face this after I made the changes to deploy the app in Cloud Foundry.

2. I have deployed the app in Cloud Foundry, but get the below message when I run the app in CF:

Logs:
{"written_at":"2024-04-25T06:25:42.949Z","written_ts":1714026342949000000,"csn_component":"-","correlation_id":"e068b7c6-eae8-497b-5b67-fd6a35c4e48f","type":"log","logger":"nodejs-logger","layer":"/Handler","level":"error","container_id":"10.32.3.5","component_type":"application","component_id":"5e07e58f-51c7-4412-b094-f1c3faadf443","component_name":"risk-management","component_instance":-1,"source_instance":-1,"organization_id":"5345543f-4ece-41a5-8d90-102a920f6be9","organization_name":"cbca00ddtrial","space_id":"ab716db3-0b31-4224-85eb-ea9432035ed3","space_name":"dev","request_id":"e068b7c6-eae8-497b-5b67-fd6a35c4e48f","msg":"GET request to launchpad.htm/launchpad.html completed with status 404 ENOENT: no such file or directory, stat '/home/vcap/app/launchpad.html'"}

3. While running the CI/CD pipeline, the Release stage faced the below error:

[2024-04-25T05:17:30.379Z] ***
[2024-04-25T05:17:30.379Z] hudson.AbortException: [cloudFoundryDeploy] Step execution failed (category: undefined). Error: running command 'cf' failed: cmd.Run() failed: exit status 1
[2024-04-25T05:17:30.379Z] ***

My project is in the below links:
https://github.com/ElAfc/RiskManagement.git

Happy to share any other info that is needed.

Any help on this would be appreciated.

Configuring SAP CI/CD pipeline for Deploying ReactJS application in Cloud Foundry

2024-04-25T12:03:01.997000+02:00

In this blog, we will discuss how to integrate SAP CI/CD pipeline for deploying ReactJS application on SAP Cloud Foundry environment.

You will learn,

How to create and build a ReactJS application.
How to configure and run SAP CI/CD Pipeline service.
How to create GitHub Webhook for automatically build, test and deploying the code changes.

Prerequisites

You have an SAP BTP Global or trial account.
Node installed in your system.
You have a GitHub account.

Setting up React Application

step 1: Create your react application using the create-react-app. The create-react-app is an excellent tool which allows you to create and run React project very quickly by wrapping all the required dependencies.

npx create-react-app reactcicd

step 2: To ensure that the application is running as expected, open the terminal and navigate to the application folder and type the below command. The application gets automatically hosted in the default server localhost:3000 and you’ll get the following screen.

npm start

step 3: Now create manifest.yml file for determining the Cloud Foundry app configurations and paste the below contents.

 ---
applications:
- name: your-app-name
path: build/
instances: 1
buildpack: https://github.com/cloudfoundry/staticfile-buildpack.git
memory: 256M

step 4: Build the application using the below command, you will see the build folder getting added to your project.

npm run build

Also create a Staticfile with the following content in the build folder as shown below

step 5: Now create a repository in your GitHub and push the changes. Make sure to remove build folder from the gitignore file since it is added default while creating the react project, we require it for deployment. For more details on how to deploy react application refer this link react-CF-deploy

Enable SAP Continuous integration and Delivery Service

step 1: Login into SAP BTP Cockpit and choose the subaccount to which you want to deploy your application.

step 2: Select Service Marketplace from the side pane and search for Continuous Integration and Delivery service. Click the create button

step 3: Create popup will appear then choose the plan you want to and click create button at the bottom. Choose View Subscription and wait until the status changes to Subscribed.

step 4: Once the status is changed to subscribed navigate to Security → Role Collections from the left-hand pane. Choose role collection CICD Service Administrator and click edit.

step 5: Navigate to users section click edit then Add a new row in the Users section table, enter your user id, Keep the identity provider as default and click save.

Configure your credentials

step 1: Go to Services → Instances and Subscriptions from the pane. Choose the application icon located next to the Continuous Integration & Delivery subscription. Now we need to add credentials for GitHub, CF and Webhook.

step 2: Let’s first go with GitHub credentials. If your GitHub repository is private, you will need to provide with the necessary credentials to access it. You can skip this in case of public repository.

step 3: In Create Credentials popup make sure you give unique name within the subaccount. Select the type as basic authentication and provide your git credentials. Use personal access token as a password. Then choose create.

step 4: Now repeat the same steps for adding CF credentials. Here you have to provide your SAP BTP cockpit username and password.

step 5: For configuring webhook credentials change the type from Basic Authentication to Webhook Secret. Then generate the webhook secret copy it somewhere safe and finally choose Create.

Add a CI/CD job

step 1: Navigate to the Jobs tab and choose the icon to add a new job. Provide unique name for the job.

step 2: Click on the icon inside the Repository input field. You will get a popup then choose add repository., Enter your git repository clone URL. You can add any name of your choice. It need not to be matched with your repo. Choose your saved credentials for git and webhook.

step 3: For Branch, enter the GitHub branch of your repository from which you want to receive push events. In this example, master. Select Cloud Foundry Environment from the dropdown in the Pipeline field.

step 4: In the BUILD section choose npm as your build tool. For Build Tool Version, select the latest node version.

step 5: Under the Release section, switch on the execution of the Deploy to Cloud Foundry Space. Since we have already given name in the manifest file, we can skip the name field.

Replace the placeholders API Endpoint, Org Name and Space with the values in the Cloud Foundry environment to which you want to deploy. You can get the values from your subaccount overview in the SAP BTP cockpit.

step 6: For Deploy Type, choose standard and select your previously created CF credentials. Leave remaining fields default then finally choose create.

Create a GitHub Webhook

GitHub webhooks allow you to automate CI/CD builds. Whenever you push changes to your GitHub repository, a webhook push event is sent to the service to trigger a build of the connected job.

step 1: To create a webhook in GitHub, you need payload URL. Select your repository and choose Webhook Data from the right pane. You will see a below popup:

step 2: Now sign in into your GitHub account. In your project, go to the Settings tab.

step 3: From the left pane, choose Webhooks then Add webhook. Enter the Payload URL, Content type from the popup and the Secret that you had saved previously. For all other settings, leave the default values and add.

Verify your Build

You have to trigger your job manually the first time after creation.

step 1: In Jobs tab, select your job and choose Run. Verify that a new tile appears in the Builds view. This tile should be marked as running.

step 2: Wait until the job has finished and verify that the build tile is marked as successful.

step 3: Navigate to your space in the SAP BTP cockpit and check the list of installed applications. Now you can see your application got added.

step 4: Select your application and launch it with the application route. You can see the react application deployed.

You have now successfully created a CI/CD pipeline and deployed your Reactjs application to SAP BTP. From now on for every commit you can see the job getting triggered with commit id displayed under builds section.

1H2024 Preview vs Prod New Release Universal Changes - Unilateral Application of Changes/Features

2024-05-18T15:26:16.584000+02:00

Hello all.

While performing initial validation of the Production 1H2024 New Release this morning, a discussion was initiated regarding how certain previously relayed changes have been adjusted without being disclosed in full and regression test allowances made to timelines for impact analysis.

There were several major feature changes, including permissions and universally applied functionality, which were repealed or adjusted in some fashion in comparison to what was provided in the New Release What's New Viewer following Prev implementation. Not in relation to known issues, but rather, at the behest of customers due to failure to consider impact to customers for universally leveraged changes without the opportunity for change mgmt with sys users.

We now have only 3 weeks to do complete E2E testing in all mods with various scenarios. This is running concurrently to business process owner exposure and experience sessions to provide insight into election options and new release mandatory feature impact/consideration for the processes they support.

How are we able to successfully regression test whatever has been changed before application in Prod? Is there a full list of all changes released by a certain date to all customers, or are changes being leveraged up and until Prod implementation? I am aware of patches and known issues, but these changes are to areas that were previously configured as universally mandated or their type was noted as Automatically Applied/Need to Enable. Now their status/type has changed and requires supplemental review and potential application.

The New Org Chart, for instance. It was not enabled in our Prod instance, while the New People Profile was. The best practice recommendation from SF was to enable or disable these two universally applied features in tandem. Yet, they deviated from their own best practice when implementing the Prod New Release. This is a poor practice for updates. This is only one situation encountered this morning, and I'm sure that the E2E post-Prod validation done by our HR customers in various modules will render significantly different results than previously encountered in Prev. This also inhibits successful contingency planning and upends previously communicated business process updates and user expectations. There is also the consideration of change requirement approval/awareness for highly regulated IT systems groups.

This change management approach really needs to be addressed. And soon. We will have customer system confidence impacts due to lack of conveyance, transparency, and cohesive actions at several levels. Any insight into planned improvements and recognition of this issue would be greatly appreciated so we're able to communicate this to our customers.

Thanks.