SAP Community - SAP Continuous Integration and Delivery

SAP Continous Integration & Delivery - GIT Hub Authentication

2024-08-08T12:29:17.587000+02:00

Hi experts,

We are trying to connect our SAP Continous Integration & Delivery with a corporate GitHub repo.

I was wondering if there is any other way apart from personal tokens to created the credentials to the repo.

In all the info I am seeing, everything is set up with personal accounts.

Many thanks,

Automating Schema Name Management in CI/CD for CAP Applications

2024-08-08T13:50:45.904000+02:00

In our CAP application, we need to explicitly set the schema name generated by the application. We've achieved this by defining the schema name in the mta.yaml file as follows:

- name: MY_APP-db
  type: com.sap.xs.hdi-container
  parameters:
    config:
      schema: MY_SCHEMA
    service: hana
    service-plan: hdi-shared

However, since our Dev and QA environments share the same HANA Cloud instance, we face an issue where the schema name must be unique across deployments.

Is there a streamlined CI/CD approach, perhaps using SAP's official CI/CD Service, to automate the use of different schema names for QA? How can we avoid manually adjusting the mta.yaml file before each deployment?

SAP Devops CI/CD - CAP project with mtaext configuration in pipeline

2024-08-24T19:27:37.870000+02:00

I have a CAP project, deploying to cloud foundry. I use SAP Continuous integration and delivery ( DevOps ) pipelines to perform the build and deployment. How can I configure my pipeline to consider a .mtaext file ? I don't see an option to do this -

SAP BTP Integration Suite artifact upload issue using CI/CD pipeline

2024-09-16T18:07:30.878000+02:00

Hi All,

I am trying to upload the integration artifacts from Github using SAP Integration Suite Artifacts CICD pipeline, however I am getting the below error in ‘Upload’ step.

The unzipped artifact folder with Manifest file are already there in the Github repository, not sure how to resolve this.

“ hudson.AbortException: [integrationArtifactUpload] Step execution failed (category: undefined). Error: HTTP POST request to https://<trialcpiaccount>/api/v1/IntegrationDesigntimeArtifacts failed with error: <?xml version='1.0' encoding='UTF-8'?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>Bad Request</code><message xml:lang="en">Integration flow project must contain a manifest file.</message></error> “

Folder structure in Github :

Would appreciate if anybody could help.

Thanks

Change Default mta.yaml filepath in BTP CICD pipeline config.yaml

2024-09-28T05:31:36.647000+02:00

I have a full stack multi-tenant project. This repository has two MTA's. One is for the CAP related artifacts which is in the root directory. The other is inside the app folder which holds the artifacts related to the frontend(UI5).

Now I need to setup my pipeline in BTP CICD. I added the github repository and tried to create a job.
Herein I understood, if I select buildtool as mta, it searches for mta.yaml file in the root directory of repository.
The thing is I need to setup two jobs one should pick mta in root directory and deploy in provider subaccount and other should pick mta from app folder and deploy it in subscriber subaccount.

Is there any other option which we can set in config.yaml file inside .pipeline folder which will override the default mta.yaml filepath or atleast set the mta file name like mta-ui.yaml ??

@Nikitha09

or is there any other way to achieve this?

SAP Continuous Integration and Delivery

Basic Authentication not working in BAS or CICD

2024-11-20T17:56:56.778000+01:00

Hi,

I am following the following tutorial with the Trial BTP Account:

https://developers.sap.com/tutorials/set-up-cicd.html

It asks in here to create credentials for Cloud Foundry. However, on the trial account, the credentials I use to log into BTP account do not work even with BAS, from where I have published the app being used in here. The credentials do not work on using them in Continuous Integration and Delivery either, as expected.

On BAS, I am only able to log into Cloud Foundry using SSO Temporary Authentication Code, but from the given authentication options, I am not sure how to log into CF.

Could someone please help?

Thanks

ci/cd deployment build failed

2024-11-29T12:09:32.776000+01:00

Hi Experts,

Can anyone help me with the below error

ERROR: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file

Build Logs (fruits #19)
Started by direct user action
Resume disabled by user, switching to high-performance, low-durability mode.
[Pipeline] Start of Pipeline
[Pipeline] library
Loading library piper-lib-os@v1.403.0
Attempting to resolve v1.403.0 from remote references...
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git ls-remote -- https://github.com/SAP/jenkins-library.git # timeout=10
Found match: refs/tags/v1.403.0 revision 364238f1541540bb2e135b56a87ad9962acd649c
Resolving tag commit... (remote references may be a lightweight tag or an annotated tag)
Creating git repository in /jenkins_home/caches/git-45f8e847db940b081a749755f5ba88e0
 > git init /jenkins_home/caches/git-45f8e847db940b081a749755f5ba88e0 # timeout=10
Setting origin to https://github.com/SAP/jenkins-library.git
 > git config remote.origin.url https://github.com/SAP/jenkins-library.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git config --get remote.origin.url # timeout=10
 > git fetch --tags --force --progress -- origin +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/tags/v1.403.0^{commit} # timeout=10
Resolved tag v1.403.0 revision 364238f1541540bb2e135b56a87ad9962acd649c
The recommended git tool is: git
No credentials specified
Cloning the remote Git repository
Cloning with configured refspecs honoured and with tags
Cloning repository https://github.com/SAP/jenkins-library.git
 > git init /jenkins_home/workspace/fruits@libs/e8d26b2abb93ac0812b8a81040340a27c7ec9deffaef1ce28ba0dc30b21c27e5 # timeout=10
Fetching upstream changes from https://github.com/SAP/jenkins-library.git
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git fetch --tags --force --progress -- https://github.com/SAP/jenkins-library.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/SAP/jenkins-library.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 364238f1541540bb2e135b56a87ad9962acd649c (v1.403.0)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 364238f1541540bb2e135b56a87ad9962acd649c # timeout=10
Commit message: "handle error while fetching working directory (#5168)"
First time build. Skipping changelog.
[Pipeline] library
Loading library cloudci-lib@v4.7.0
Attempting to resolve v4.7.0 from remote references...
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git ls-remote -- http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git # timeout=10
Found match: refs/tags/v4.7.0 revision 6542a87a2af31755b99f5e853c4dacab9769ca27
Resolving tag commit... (remote references may be a lightweight tag or an annotated tag)
Creating git repository in /jenkins_home/caches/git-b339b888659ec5714c76821992280a0e
 > git init /jenkins_home/caches/git-b339b888659ec5714c76821992280a0e # timeout=10
Setting origin to http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git
 > git config remote.origin.url http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git config --get remote.origin.url # timeout=10
 > git fetch --tags --force --progress -- origin +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/tags/v4.7.0^{commit} # timeout=10
Resolved tag v4.7.0 revision 6542a87a2af31755b99f5e853c4dacab9769ca27
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning with configured refspecs honoured and with tags
Cloning repository http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git
 > git init /jenkins_home/workspace/fruits@libs/6d4311b5453c7045963a824fe7a1ae2d1efd853e23990e74c7648494558625bc # timeout=10
Fetching upstream changes from http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git
 > git --version # timeout=10
 > git --version # 'git version 2.45.2'
 > git fetch --tags --force --progress -- http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 6542a87a2af31755b99f5e853c4dacab9769ca27 (v4.7.0)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6542a87a2af31755b99f5e853c4dacab9769ca27 # timeout=10
Commit message: "chore(deps): update dockerimages-minor-patch-digest-updates (#447)"
First time build. Skipping changelog.
[Pipeline] node
Running on Jenkins in /jenkins_home/workspace/fruits
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Init)
[Pipeline] script
[Pipeline] {
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
[2024-11-29T10:46:09.839Z] Created Pod: kubernetes steward-run-59e8z-main-55m7c/fruits-19-hx583-vxnth-2g5g3
[2024-11-29T10:46:12.498Z] Agent fruits-19-hx583-vxnth-2g5g3 is provisioned from template fruits_19-hx583-vxnth
[2024-11-29T10:46:12.509Z] Running on fruits-19-hx583-vxnth-2g5g3 in /home/jenkins/agent/workspace/fruits
[Pipeline] {
[Pipeline] container
[Pipeline] {
[Pipeline] sh
[2024-11-29T10:46:13.518Z] + proxy-starter '-image=haproxy@sha256:ce0a582c7e21309e15f221c032ccdd06391339f45a673f3a2081513b934fe2cc' '-v=0'
[2024-11-29T10:46:13.519Z] I1129 10:46:13.221648      20 proxystarter.go:74] No Cloud Connector secrets defined, no need for the proxy
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] readJSON
[Pipeline] checkout
[2024-11-29T10:46:13.938Z] The recommended git tool is: NONE
[2024-11-29T10:46:13.972Z] using credential github
[2024-11-29T10:46:14.024Z] Cloning the remote Git repository
[2024-11-29T10:46:14.029Z] Cloning repository https://github.com/kiranlingala12/fruits.git
[2024-11-29T10:46:14.030Z]  > git init /jenkins_home/workspace/fruits # timeout=10
[2024-11-29T10:46:14.042Z] Fetching upstream changes from https://github.com/kiranlingala12/fruits.git
[2024-11-29T10:46:14.042Z]  > git --version # timeout=10
[2024-11-29T10:46:14.049Z]  > git --version # 'git version 2.45.2'
[2024-11-29T10:46:14.050Z] using GIT_ASKPASS to set credentials 
[2024-11-29T10:46:14.058Z]  > git fetch --tags --force --progress -- https://github.com/kiranlingala12/fruits.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2024-11-29T10:46:14.271Z]  > git config remote.origin.url https://github.com/kiranlingala12/fruits.git # timeout=10
[2024-11-29T10:46:14.283Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2024-11-29T10:46:14.305Z] Avoid second fetch
[2024-11-29T10:46:14.307Z]  > git rev-parse origin/dev_branch^{commit} # timeout=10
[2024-11-29T10:46:14.342Z] Checking out Revision 3a60176ab47edf5b422d634bf17f2aecc6349364 (origin/dev_branch)
[2024-11-29T10:46:14.343Z]  > git config core.sparsecheckout # timeout=10
[2024-11-29T10:46:14.364Z]  > git checkout -f 3a60176ab47edf5b422d634bf17f2aecc6349364 # timeout=10
[2024-11-29T10:46:14.431Z] Commit message: "testing sravani"
[2024-11-29T10:46:14.434Z] First time build. Skipping changelog.
[Pipeline] libraryResource
[Pipeline] sh
[2024-11-29T10:46:14.852Z] INFO GIT_COMMIT_TO_BE_BUILT (dev_branch / 3a60176ab47edf5b422d634bf17f2aecc6349364) is reachable from the configured branch (dev_branch).
[Pipeline] sh
[2024-11-29T10:46:15.147Z] + git config -f .gitmodules --get-regexp ^submodule..+.url
[2024-11-29T10:46:15.147Z] + true
[Pipeline] echo
[2024-11-29T10:46:15.191Z] Writing pipeline configuration from UI/API to .pipeline/config.yml.
[Pipeline] writeFile
[Pipeline] fileExists
[Pipeline] echo
[2024-11-29T10:46:15.355Z] Using Job Editor Configuration Mode
[Pipeline] fileExists
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] libraryResource
[Pipeline] writeYaml
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] echo
[2024-11-29T10:46:18.163Z] INFO: found image 'devxci/mbtci-java11-node20@sha256:141f685dc9dc9cf27c60c6e8c2b5aab7d0a683de7d769abe2dd595ab5da95282' for imagePath 'buildToolImages.MBTJ11N20.buildTool'.
[Pipeline] echo
[2024-11-29T10:46:18.202Z] [INFO] using build-tool-image 'devxci/mbtci-java11-node20@sha256:141f685dc9dc9cf27c60c6e8c2b5aab7d0a683de7d769abe2dd595ab5da95282'.
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] echo
[2024-11-29T10:46:18.415Z] INFO: found image 'ppiper/node-browsers@sha256:0eac2b307a9b1349e26fe4fd2c8f83bc3306cf66b240f9410d47d91ef9849d89' for imagePath 'buildToolImages.MBTJ11N20.nodeBrowser'.
[Pipeline] echo
[2024-11-29T10:46:18.445Z] [INFO] using node-browser-image 'ppiper/node-browsers@sha256:0eac2b307a9b1349e26fe4fd2c8f83bc3306cf66b240f9410d47d91ef9849d89'.
[Pipeline] sh
[2024-11-29T10:46:18.840Z] + git rev-parse HEAD
[Pipeline] sh
[2024-11-29T10:46:19.893Z] + head -n 1
[2024-11-29T10:46:19.899Z] + git show -s --format=%B 3a60176ab47edf5b422d634bf17f2aecc6349364
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] writeYaml
[Pipeline] echo
[2024-11-29T10:46:21.736Z] Stash content: checkoutstash (includes: **/*, excludes: cloudcitransfer/**/*, allowEmpty: null)
[Pipeline] stash
[2024-11-29T10:46:21.825Z] Stashed 83 file(s)
[Pipeline] dir
[2024-11-29T10:46:21.851Z] Running in /jenkins_home/workspace/fruits/cloudcitransfer
[Pipeline] {
[Pipeline] writeFile
[Pipeline] writeFile
[Pipeline] }
[Pipeline] // dir
[Pipeline] echo
[2024-11-29T10:46:22.066Z] Stash content: cloudcitransfer (includes: cloudcitransfer/**/*, excludes: cloudcitransfer/**/node_modules/**, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:46:22.101Z] Stashed 2 file(s)
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] lock
[2024-11-29T10:46:30.399Z] Trying to acquire lock on [Resource: fruits/1]
[2024-11-29T10:46:30.420Z] Resource [fruits/1] did not exist. Created.
[2024-11-29T10:46:30.433Z] Lock acquired on [Resource: fruits/1]
[Pipeline] {
[Pipeline] milestone
[2024-11-29T10:46:30.513Z] Trying to pass milestone 1
[Pipeline] node
[2024-11-29T10:46:30.581Z] Running on Jenkins in /jenkins_home/workspace/fruits@2
[Pipeline] {
[Pipeline] deleteDir
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] echo
[2024-11-29T10:46:30.663Z] Unstash content: checkoutstash
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:46:32.128Z] --- Begin library step of: setupCommonPipelineEnvironment ---
[Pipeline] fileExists
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] writeFile
[Pipeline] fileExists
[Pipeline] readFile
[Pipeline] writeFile
[Pipeline] fileExists
[Pipeline] readFile
[Pipeline] writeFile
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] echo
[2024-11-29T10:46:32.748Z] Loading configuration file '.pipeline/cicdCommonBaseDefaults.yml'
[Pipeline] readYaml
[Pipeline] echo
[2024-11-29T10:46:32.968Z] Loading configuration file '.pipeline/cicdPipelineSpecificDefaults.yml'
[Pipeline] readYaml
[Pipeline] echo
[2024-11-29T10:46:33.471Z] --- Begin library step of: piperLoadGlobalExtensions ---
[Pipeline] echo
[2024-11-29T10:46:33.630Z] --- End library step of: piperLoadGlobalExtensions ---
[Pipeline] echo
[2024-11-29T10:46:33.661Z] Stash content: pipelineConfigAndTests (includes: .pipeline/**, excludes: , useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:46:33.694Z] Stashed 6 file(s)
[Pipeline] echo
[2024-11-29T10:46:33.880Z] --- End library step of: setupCommonPipelineEnvironment ---
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] writeFile
[Pipeline] sh
[2024-11-29T10:46:35.528Z] + '[' -x ./piper ]
[Pipeline] echo
[2024-11-29T10:46:35.550Z] Unstash content: piper-bin
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:46:35.630Z] Unstash failed: piper-bin (No such saved stash ‘piper-bin’)
[Pipeline] sh
[2024-11-29T10:46:35.959Z] + curl --insecure --silent --retry 5 --retry-max-time 240 --location --write-out '%{http_code}' --output piper https://github.com/SAP/jenkins-library/releases/download/v1.403.0/piper
[Pipeline] sh
[2024-11-29T10:46:36.492Z] + chmod +x piper
[Pipeline] sh
[2024-11-29T10:46:36.771Z] + ./piper version
[2024-11-29T10:46:36.772Z] time="2024-11-29T10:46:36Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[Pipeline] echo
[2024-11-29T10:46:36.795Z] Piper go binary version: piper-version:
[2024-11-29T10:46:36.796Z]     commit: "364238f1541540bb2e135b56a87ad9962acd649c"
[2024-11-29T10:46:36.796Z]     tag: "<n/a>"
[2024-11-29T10:46:36.797Z] 
[Pipeline] echo
[2024-11-29T10:46:36.834Z] Stash content: piper-bin (includes: piper, excludes: , useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:41.807Z] Stashed 1 file(s)
[Pipeline] sh
[2024-11-29T10:46:42.103Z] + ./piper checkIfStepActive --stageConfig .pipeline/stage_conditions.yaml --useV1 --stageOutputFile .pipeline/stage_out.json --stepOutputFile .pipeline/step_out.json --stage _ --step _ --defaultConfig .pipeline/.pipeline/cicdCommonBaseDefaults.yml,.pipeline/.pipeline/cicdPipelineSpecificDefaults.yml --ignoreCustomDefaults
[2024-11-29T10:46:42.104Z] time="2024-11-29T10:46:42Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[2024-11-29T10:46:42.105Z] time="2024-11-29T10:46:42Z" level=warning msg="Please do not use --useV1 flag since it is deprecated and will be removed in future releases" library=SAP/jenkins-library
[2024-11-29T10:46:42.105Z] time="2024-11-29T10:46:42Z" level=info msg="Project config: '.pipeline/config.yml'" library=SAP/jenkins-library
[2024-11-29T10:46:42.355Z] time="2024-11-29T10:46:42Z" level=info msg="Writing stage condition file .pipeline/stage_out.json" library=SAP/jenkins-library
[2024-11-29T10:46:42.357Z] time="2024-11-29T10:46:42Z" level=info msg="Writing step condition file .pipeline/step_out.json" library=SAP/jenkins-library
[Pipeline] readJSON
[Pipeline] readJSON
[Pipeline] echo
[2024-11-29T10:46:44.661Z] --- Begin library step of: pipelineStashFilesBeforeBuild ---
[Pipeline] echo
[2024-11-29T10:46:44.817Z] Stash content: buildDescriptor (includes: **/pom.xml, **/.mvn/**, **/assembly.xml, **/.swagger-codegen-ignore, **/package.json, **/requirements.txt, **/setup.py, **/mta*.y*ml, **/.npmrc, **/Dockerfile, .hadolint.yaml, **/VERSION, **/version.txt, **/Gopkg.*, **/dub.json, **/dub.sdl, **/build.sbt, **/sbtDescriptor.json, **/project/*, **/ui5.yaml, **/ui5.yml, excludes: **/node_modules/**/package.json, cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:44.840Z] Stashed 5 file(s)
[Pipeline] echo
[2024-11-29T10:46:44.852Z] Stash content: deployDescriptor (includes: **/manifest*.y*ml, **/*.mtaext.y*ml, **/*.mtaext, **/xs-app.json, helm/**, **/*.y*ml, **/*.tpl, **/*.tgz, excludes: cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:44.879Z] Stashed 13 file(s)
[Pipeline] echo
[2024-11-29T10:46:44.891Z] Stash content: git (includes: .git/**, excludes: cloudcitransfer/**/*, useDefaultExcludes: false, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:44.938Z] Stashed 27 file(s)
[Pipeline] echo
[2024-11-29T10:46:44.948Z] Stash content: opensourceConfiguration (includes: **/srcclr.yml, **/vulas-custom.properties, **/.nsprc, **/.retireignore, **/.retireignore.json, **/.snyk, **/wss-unified-agent.config, **/vendor/**/*, excludes: cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[Pipeline] echo
[2024-11-29T10:46:44.981Z] [pipelineStashFilesBeforeBuild] no files detected for stash 'opensourceConfiguration': opensourceConfiguration (No files included in stash ‘opensourceConfiguration’)
[Pipeline] echo
[2024-11-29T10:46:45.000Z] Stash content: pipelineConfigAndTests (includes: .pipeline/**, excludes: cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:45.033Z] Warning: overwriting stash ‘pipelineConfigAndTests’
[2024-11-29T10:46:45.048Z] Stashed 9 file(s)
[Pipeline] echo
[2024-11-29T10:46:45.072Z] Stash content: securityDescriptor (includes: **/xs-security.json, excludes: cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:45.114Z] Stashed 1 file(s)
[Pipeline] echo
[2024-11-29T10:46:45.136Z] Stash content: tests (includes: **/pom.xml, **/*.json, **/*.xml, **/src/**, **/node_modules/**, **/specs/**, **/env/**, **/*.js, **/tests/**, **/*.html, **/*.css, **/*.properties, **/*.cds, excludes: cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:45.227Z] Stashed 38 file(s)
[Pipeline] echo
[2024-11-29T10:46:45.263Z] Stash content: checkmarx (includes: **/*.js, **/*.scala, **/*.py, **/*.go, **/*.xml, **/*.html, **/*.d, **/*.di, **/*.ts, excludes: **/*.mockserver.js, node_modules/**/*.js, cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:45.319Z] Stashed 14 file(s)
[Pipeline] echo
[2024-11-29T10:46:45.340Z] Stash content: checkmarxOne (includes: **/*.js, **/*.scala, **/*.py, **/*.go, **/*.xml, **/*.html, **/*.d, **/*.di, **/*.ts, excludes: **/*.mockserver.js, node_modules/**/*.js, cloudcitransfer/**/*, useDefaultExcludes: true, allowEmpty: false)
[Pipeline] stash
[2024-11-29T10:46:45.376Z] Stashed 14 file(s)
[Pipeline] echo
[2024-11-29T10:46:45.387Z] --- End library step of: pipelineStashFilesBeforeBuild ---
[Pipeline] echo
[2024-11-29T10:46:45.418Z] Stash content: source (includes: **/*, excludes: .pipeline/**)
[Pipeline] stash
[2024-11-29T10:46:49.250Z] Stashed 53 file(s)
[Pipeline] deleteDir
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[2024-11-29T10:46:49.333Z] Lock released on resource [Resource: fruits/1]
[Pipeline] // lock
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] writeJSON
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withCredentials
[Pipeline] {
[Pipeline] echo
[2024-11-29T10:46:49.850Z] [INFO] No runFirst command defined for current stage (Build). Will not execute additional commands step
[Pipeline] lock
[2024-11-29T10:46:50.220Z] Trying to acquire lock on [Resource: fruits]
[2024-11-29T10:46:50.227Z] Resource [fruits] did not exist. Created.
[2024-11-29T10:46:50.230Z] Lock acquired on [Resource: fruits]
[Pipeline] {
[Pipeline] node
[2024-11-29T10:46:50.270Z] Running on Jenkins in /jenkins_home/workspace/fruits@2
[Pipeline] {
[Pipeline] deleteDir
[Pipeline] echo
[2024-11-29T10:46:50.327Z] Unstash content: pipelineConfigAndTests
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:46:50.368Z] Unstash content: source
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:46:50.933Z] Unstash content: cloudcitransfer
[Pipeline] unstash
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] echo
[2024-11-29T10:46:51.681Z] --- Begin library step of: buildExecute ---
[Pipeline] echo
[2024-11-29T10:46:52.441Z] --- Begin library step of: mtaBuild ---
[Pipeline] sh
[2024-11-29T10:46:52.742Z] + '[' -x ./piper ]
[Pipeline] echo
[2024-11-29T10:46:52.776Z] Found piper binary in the workspace - skipping unstash
[Pipeline] echo
[2024-11-29T10:46:52.828Z] Unstash content: pipelineConfigAndTests
[Pipeline] unstash
[Pipeline] libraryResource
[Pipeline] writeFile
[Pipeline] echo
[2024-11-29T10:46:53.001Z] Step params [:]
[Pipeline] withEnv
[Pipeline] {
[Pipeline] echo
[2024-11-29T10:46:53.112Z] PIPER_parametersJSON: {}
[Pipeline] sh
[2024-11-29T10:46:53.422Z] + ./piper getConfig --contextConfig --stepMetadata .pipeline/tmp/metadata/mtaBuild.yaml --defaultConfig .pipeline/.pipeline/cicdCommonBaseDefaults.yml,.pipeline/.pipeline/cicdPipelineSpecificDefaults.yml --ignoreCustomDefaults
[2024-11-29T10:46:53.422Z] time="2024-11-29T10:46:53Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[2024-11-29T10:46:53.422Z] time="2024-11-29T10:46:53Z" level=info msg="Printing stepName " library=SAP/jenkins-library
[Pipeline] readJSON
[Pipeline] echo
[2024-11-29T10:46:53.512Z] Context Config: [contextConfig:true, defaultConfig:[.pipeline/.pipeline/cicdCommonBaseDefaults.yml, .pipeline/.pipeline/cicdPipelineSpecificDefaults.yml], dockerImage:devxci/mbtci-java11-node20@sha256:141f685dc9dc9cf27c60c6e8c2b5aab7d0a683de7d769abe2dd595ab5da95282, ignoreCustomDefaults:true, stepMetadata:.pipeline/tmp/metadata/mtaBuild.yaml]
[Pipeline] echo
[2024-11-29T10:46:53.572Z] [INFO] executing pipeline step 'mtaBuild' with docker image 'devxci/mbtci-java11-node20@sha256:141f685dc9dc9cf27c60c6e8c2b5aab7d0a683de7d769abe2dd595ab5da95282'
[Pipeline] echo
[2024-11-29T10:46:54.506Z] --- Begin library step of: dockerExecute ---
[Pipeline] echo
[2024-11-29T10:46:55.605Z] --- Begin library step of: dockerExecuteOnKubernetes ---
[Pipeline] echo
[2024-11-29T10:46:55.850Z] Stash content: workspace-65c3ec26-11a0-4305-979a-67238d206016 (includes: **/*, excludes: nohup.out, useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:47:00.566Z] Stashed 65 file(s)
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
[2024-11-29T10:47:03.118Z] Created Pod: kubernetes steward-run-59e8z-main-55m7c/dynamic-agent-65c3ec26-11a0-4305-979a-67238d206016-r1483-wqhpb
[2024-11-29T10:47:16.300Z] Still waiting to schedule task
[2024-11-29T10:47:16.301Z] Waiting for next available executor on ‘dynamic-agent-65c3ec26-11a0-4305-979a-67238d206016-r1483-wqhpb’
[2024-11-29T10:47:29.675Z] Agent dynamic-agent-65c3ec26-11a0-4305-979a-67238d206016-r1483-wqhpb is provisioned from template dynamic-agent-65c3ec26-11a0-4305-979a-67238d206016-r1483
[2024-11-29T10:47:29.679Z] Running on dynamic-agent-65c3ec26-11a0-4305-979a-67238d206016-r1483-wqhpb in /home/jenkins/agent/workspace/fruits
[Pipeline] {
[Pipeline] echo
[2024-11-29T10:47:29.724Z] ContainerConfig: [name:container-exec]
[Pipeline] container
[Pipeline] {
[Pipeline] echo
[2024-11-29T10:47:29.760Z] Unstash content: workspace-65c3ec26-11a0-4305-979a-67238d206016
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:47:33.552Z] invalidate stash workspace-65c3ec26-11a0-4305-979a-67238d206016
[Pipeline] echo
[2024-11-29T10:47:33.587Z] Stash content: workspace-65c3ec26-11a0-4305-979a-67238d206016 (includes: **/*.*, excludes: **/*, useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:47:33.620Z] Warning: overwriting stash ‘workspace-65c3ec26-11a0-4305-979a-67238d206016’
[2024-11-29T10:47:34.241Z] Stashed 0 file(s)
[Pipeline] echo
[2024-11-29T10:47:34.259Z] [INFO][dockerExecute] Executing inside a Kubernetes Pod. Docker image: devxci/mbtci-java11-node20@sha256:141f685dc9dc9cf27c60c6e8c2b5aab7d0a683de7d769abe2dd595ab5da95282
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
[2024-11-29T10:47:35.528Z] + ./piper writePipelineEnv
[2024-11-29T10:47:35.529Z] time="2024-11-29T10:47:35Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] echo
[2024-11-29T10:47:35.663Z] Unstash content: pipelineStepReports
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:47:35.714Z] Unstash failed: pipelineStepReports (No such saved stash ‘pipelineStepReports’)
[Pipeline] withCredentials
[Pipeline] {
[Pipeline] sh
[2024-11-29T10:47:36.510Z] + ./piper mtaBuild --defaultConfig .pipeline/.pipeline/cicdCommonBaseDefaults.yml,.pipeline/.pipeline/cicdPipelineSpecificDefaults.yml --ignoreCustomDefaults
[2024-11-29T10:47:36.513Z] time="2024-11-29T10:47:36Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[2024-11-29T10:47:36.514Z] info  mtaBuild - running command: npm config get registry -ws=false -iwr
[2024-11-29T10:47:36.780Z] info  mtaBuild - Discovered pre-configured npm registry registry with value https://registry.npmjs.org/
[2024-11-29T10:47:36.781Z] 
[2024-11-29T10:47:36.781Z] info  mtaBuild - "mta.yaml" file not found in project sources
[2024-11-29T10:47:36.781Z] info  mtaBuild - fatal error: errorDetails{"category":"undefined","correlationId":"n/a","error":"'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file","library":"SAP/jenkins-library","message":"failed to execute mta build","result":"failure","stepName":"mtaBuild","time":"2024-11-29T10:47:36.540982438Z"}
[2024-11-29T10:47:36.781Z] fatal mtaBuild - failed to execute mta build - 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
[2024-11-29T10:47:36.781Z] info  mtaBuild - persisting reports to GCS is disabled, because gcsBucketId is empty
[2024-11-29T10:47:36.782Z] info  mtaBuild - Step telemetry data:{"StepStartTime":"2024-11-29 10:47:36.340413537 +0000 UTC","PipelineURLHash":"50f013532a9770a2c2cfdc38b7581dd01df69b70","BuildURLHash":"50f013532a9770a2c2cfdc38b7581dd01df69b70","StageName":"Build","StepName":"mtaBuild","ErrorCode":"1","StepDuration":"201","ErrorCategory":"undefined","CorrelationID":"n/a","PiperCommitHash":"364238f1541540bb2e135b56a87ad9962acd649c","ErrorDetail":{"category":"undefined","correlationId":"n/a","error":"'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file","library":"SAP/jenkins-library","message":"failed to execute mta build","result":"failure","stepName":"mtaBuild","time":"2024-11-29T10:47:36.540982438Z"}}
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] sh
[2024-11-29T10:47:37.652Z] + ./piper readPipelineEnv
[2024-11-29T10:47:37.657Z] time="2024-11-29T10:47:37Z" level=info msg="Version 364238f1541540bb2e135b56a87ad9962acd649c" library=SAP/jenkins-library
[Pipeline] readJSON
[Pipeline] echo
[2024-11-29T10:47:37.751Z] Transfer Influx data
[Pipeline] findFiles
[Pipeline] echo
[2024-11-29T10:47:37.839Z] Stash content: pipelineStepReports (includes: .pipeline/stepReports/**, excludes: , useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:47:37.899Z] Stashed 0 file(s)
[Pipeline] fileExists
[Pipeline] readJSON
[Pipeline] error
[Pipeline] sh
[Pipeline] echo
[2024-11-29T10:47:38.774Z] Stash content: container-65c3ec26-11a0-4305-979a-67238d206016 (includes: **/*, excludes: **/node_modules/**,nohup.out,.git/**, useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:47:43.215Z] Stashed 73 file(s)
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] echo
[2024-11-29T10:47:43.646Z] Unstash content: container-65c3ec26-11a0-4305-979a-67238d206016
[Pipeline] unstash
[Pipeline] echo
[2024-11-29T10:47:44.439Z] invalidate stash container-65c3ec26-11a0-4305-979a-67238d206016
[Pipeline] echo
[2024-11-29T10:47:44.482Z] Stash content: container-65c3ec26-11a0-4305-979a-67238d206016 (includes: **/*.*, excludes: **/*, useDefaultExcludes: true, allowEmpty: true)
[Pipeline] stash
[2024-11-29T10:47:44.515Z] Warning: overwriting stash ‘container-65c3ec26-11a0-4305-979a-67238d206016’
[2024-11-29T10:47:44.527Z] Stashed 0 file(s)
[Pipeline] libraryResource
[Pipeline] echo
[2024-11-29T10:47:44.659Z] ----------------------------------------------------------
[2024-11-29T10:47:44.659Z] --- An error occurred in the library step: dockerExecuteOnKubernetes
[2024-11-29T10:47:44.659Z] ----------------------------------------------------------
[2024-11-29T10:47:44.659Z] 
[2024-11-29T10:47:44.659Z] The following parameters were available to the step:
[2024-11-29T10:47:44.659Z] ***
[2024-11-29T10:47:44.659Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2024-11-29T10:47:44.659Z] *** WARNING: this may reveal sensitive information. ***
[2024-11-29T10:47:44.660Z] ***
[2024-11-29T10:47:44.660Z] 
[2024-11-29T10:47:44.660Z] The error was:
[2024-11-29T10:47:44.660Z] ***
[2024-11-29T10:47:44.660Z] hudson.AbortException: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
[2024-11-29T10:47:44.660Z] ***
[2024-11-29T10:47:44.660Z] 
[2024-11-29T10:47:44.660Z] Further information:
[2024-11-29T10:47:44.660Z] * Documentation of library step dockerExecuteOnKubernetes: https://sap.github.io/jenkins-library/steps/dockerExecuteOnKubernetes/
[2024-11-29T10:47:44.660Z] * Source code of library step dockerExecuteOnKubernetes: https://github.com/SAP/jenkins-library/blob/master/vars/dockerExecuteOnKubernetes.groovy
[2024-11-29T10:47:44.660Z] * Library documentation: https://sap.github.io/jenkins-library/
[2024-11-29T10:47:44.660Z] * Library repository: https://github.com/SAP/jenkins-library/
[2024-11-29T10:47:44.660Z] 
[2024-11-29T10:47:44.661Z] ----------------------------------------------------------
[2024-11-29T10:47:44.661Z] --- End library step of: dockerExecuteOnKubernetes ---
[Pipeline] libraryResource
[Pipeline] echo
[2024-11-29T10:47:44.826Z] ----------------------------------------------------------
[2024-11-29T10:47:44.826Z] --- An error occurred in the library step: dockerExecute
[2024-11-29T10:47:44.826Z] ----------------------------------------------------------
[2024-11-29T10:47:44.827Z] 
[2024-11-29T10:47:44.827Z] The following parameters were available to the step:
[2024-11-29T10:47:44.827Z] ***
[2024-11-29T10:47:44.827Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2024-11-29T10:47:44.827Z] *** WARNING: this may reveal sensitive information. ***
[2024-11-29T10:47:44.827Z] ***
[2024-11-29T10:47:44.827Z] 
[2024-11-29T10:47:44.827Z] The error was:
[2024-11-29T10:47:44.829Z] ***
[2024-11-29T10:47:44.829Z] hudson.AbortException: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
[2024-11-29T10:47:44.831Z] ***
[2024-11-29T10:47:44.831Z] 
[2024-11-29T10:47:44.831Z] Further information:
[2024-11-29T10:47:44.832Z] * Documentation of library step dockerExecute: https://sap.github.io/jenkins-library/steps/dockerExecute/
[2024-11-29T10:47:44.832Z] * Source code of library step dockerExecute: https://github.com/SAP/jenkins-library/blob/master/vars/dockerExecute.groovy
[2024-11-29T10:47:44.832Z] * Library documentation: https://sap.github.io/jenkins-library/
[2024-11-29T10:47:44.832Z] * Library repository: https://github.com/SAP/jenkins-library/
[2024-11-29T10:47:44.832Z] 
[2024-11-29T10:47:44.832Z] ----------------------------------------------------------
[2024-11-29T10:47:44.832Z] --- End library step of: dockerExecute ---
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] libraryResource
[Pipeline] echo
[2024-11-29T10:47:44.974Z] ----------------------------------------------------------
[2024-11-29T10:47:44.974Z] --- An error occurred in the library step: mtaBuild
[2024-11-29T10:47:44.974Z] ----------------------------------------------------------
[2024-11-29T10:47:44.975Z] 
[2024-11-29T10:47:44.975Z] The following parameters were available to the step:
[2024-11-29T10:47:44.975Z] ***
[2024-11-29T10:47:44.975Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2024-11-29T10:47:44.975Z] *** WARNING: this may reveal sensitive information. ***
[2024-11-29T10:47:44.975Z] ***
[2024-11-29T10:47:44.975Z] 
[2024-11-29T10:47:44.975Z] The error was:
[2024-11-29T10:47:44.975Z] ***
[2024-11-29T10:47:44.976Z] hudson.AbortException: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
[2024-11-29T10:47:44.976Z] ***
[2024-11-29T10:47:44.976Z] 
[2024-11-29T10:47:44.976Z] Further information:
[2024-11-29T10:47:44.976Z] * Documentation of library step mtaBuild: https://sap.github.io/jenkins-library/steps/mtaBuild/
[2024-11-29T10:47:44.976Z] * Source code of library step mtaBuild: https://github.com/SAP/jenkins-library/blob/master/vars/mtaBuild.groovy
[2024-11-29T10:47:44.976Z] * Library documentation: https://sap.github.io/jenkins-library/
[2024-11-29T10:47:44.977Z] * Library repository: https://github.com/SAP/jenkins-library/
[2024-11-29T10:47:44.977Z] 
[2024-11-29T10:47:44.977Z] ----------------------------------------------------------
[2024-11-29T10:47:44.977Z] --- End library step of: mtaBuild ---
[Pipeline] libraryResource
[Pipeline] echo
[2024-11-29T10:47:45.062Z] ----------------------------------------------------------
[2024-11-29T10:47:45.062Z] --- An error occurred in the library step: buildExecute
[2024-11-29T10:47:45.062Z] ----------------------------------------------------------
[2024-11-29T10:47:45.062Z] 
[2024-11-29T10:47:45.062Z] The following parameters were available to the step:
[2024-11-29T10:47:45.062Z] ***
[2024-11-29T10:47:45.062Z] *** to show step parameters, set verbose:true in general pipeline configuration
[2024-11-29T10:47:45.063Z] *** WARNING: this may reveal sensitive information. ***
[2024-11-29T10:47:45.063Z] ***
[2024-11-29T10:47:45.063Z] 
[2024-11-29T10:47:45.063Z] The error was:
[2024-11-29T10:47:45.063Z] ***
[2024-11-29T10:47:45.063Z] hudson.AbortException: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
[2024-11-29T10:47:45.063Z] ***
[2024-11-29T10:47:45.063Z] 
[2024-11-29T10:47:45.063Z] Further information:
[2024-11-29T10:47:45.063Z] * Documentation of library step buildExecute: https://sap.github.io/jenkins-library/steps/buildExecute/
[2024-11-29T10:47:45.063Z] * Source code of library step buildExecute: https://github.com/SAP/jenkins-library/blob/master/vars/buildExecute.groovy
[2024-11-29T10:47:45.063Z] * Library documentation: https://sap.github.io/jenkins-library/
[2024-11-29T10:47:45.064Z] * Library repository: https://github.com/SAP/jenkins-library/
[2024-11-29T10:47:45.064Z] 
[2024-11-29T10:47:45.064Z] ----------------------------------------------------------
[2024-11-29T10:47:45.064Z] --- End library step of: buildExecute ---
[Pipeline] echo
[2024-11-29T10:47:45.099Z] Stash content: cloudcitransfer (includes: cloudcitransfer/**/*, excludes: cloudcitransfer/**/node_modules/**)
[Pipeline] stash
[2024-11-29T10:47:45.121Z] Warning: overwriting stash ‘cloudcitransfer’
[2024-11-29T10:47:45.122Z] Stashed 2 file(s)
[Pipeline] deleteDir
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[2024-11-29T10:47:45.306Z] Lock released on resource [Resource: fruits]
[Pipeline] // lock
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Additional Unit Tests)
Stage "Additional Unit Tests" skipped due to earlier failure(s)
[Pipeline] getContext
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Malware Scan)
Stage "Malware Scan" skipped due to earlier failure(s)
[Pipeline] getContext
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Acceptance)
Stage "Acceptance" skipped due to earlier failure(s)
[Pipeline] getContext
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Compliance)
Stage "Compliance" skipped due to earlier failure(s)
[Pipeline] getContext
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Release)
Stage "Release" skipped due to earlier failure(s)
[Pipeline] getContext
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: [mtaBuild] Step execution failed (category: undefined). Error: 'mta.yaml' not found in project sources and 'applicationName' not provided as parameter - cannot generate 'mta.yaml' file
Finished: FAILURE

Thanks,

reddy

Facing issue with BTP CI/CD Pipeline Initialization

2025-01-06T10:09:39.381000+01:00

Hi Team,

Can anyone help me on the below issue.

Here i am implementing ci-cd process facing below error.

[2025-01-06T04:18:50.794Z] stderr: remote: Support for password authentication was removed on August 13, 2021.
[2025-01-06T04:18:50.795Z] remote: Please see https://docs.github.com/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
[2025-01-06T04:18:50.795Z] fatal: Authentication failed for 'https://github.com/My BU/fruits.git/'

Here my GitHub repo is private one.

Thanks,

Sravani

SAP Test Automation – What tools are available?

2025-02-13T16:51:46.734000+01:00

Some of you are probably familiar with SAP Enterprise Continuous Testing (ECT) or also known using the name Tricentis Tosca. This tool is already on the market for several years and it is well known with the test automation community. It can be fully integrated with Solution Manger and there is also lite version available named “Tricentis Test Automation integrated with SAP Solution Manager”. The lite version is still fairly powerful, and it comes at no cost for customers, that do have Enterprise Support agreements with SAP.

Some while ago SAP in partnership with Tricentis have issued a new cloud offering called “Tricentis Test Automation integrated with SAP Cloud ALM”, I will refer to “TTA with CALM” in my blog to make it simpler. Some people also refer to this product as Tosca Cloud. But it isn’t the official naming used by neither SAP, neither Tricentis. This comes also free of charge for customers with Enterprise Support agreements. However, based on our experience this also comes without any costs to customers with Preferred Success and possibly to all customers using SAP Cloud ALM. However, I’m unable to verify this statement. And by the way SAP Cloud ALM is a very powerful tool and lot of our customers are unaware that they are eligible to use it free of charge as long as they have any Cloud product from SAP. I really recommend checking the eligibility with your SAP Account Executive.

Very recently SAP (I believe some time in 2024) SAP has also released a paid version called “SAP Test Automation by Tricentis (STA)”.

The below picture nicely depicts different product options and some high-level limitations.

Lot of customers are asking us for an advice on what tool do we recommend. Whether they should opt for the on-premise SAP ECT (Tosca) or they should go for SAP STA (Cloud Tosca) integrated with SAP Cloud ALM. Or their free of charge alternatives TTA

This isn’t really an easy question. However we have recently had a chance to work with the latest Cloud version, so I could provide my angle.

Firstly, I have to say that the cloud version is getting constant updates with every single quarter. And really, I believe SAP and Tricentis are investing a lot in order to make both tools comparable. The question we often get is, whether STA is on par with ECT. Well, a huge progress was recently made when STA & TTA with CALM also natively support automation of SAP GUI. Unfortunately, previously only automation of SAP Fiori was possible, which obviously had a bit of limited use for SAP customers, as many of them are in sort of hybrid phase and rely both on Fiori and GUI still.

Below picture illustrates STA roadmap in 2024 and beginning of 2025

If you need to decide on which tool you as organization want to use. You have to first understand what applications and process you want to test with test automation solution. Potentially there is also fifth SAP option and that is applicable for customers on S/4 HANA Public Cloud. If you run on S/4 HANA Public Cloud, then you can use so call „S4 HANA Cloud Test Automation Tool“. Maybe at some point this offering will contain rich features, I believe at this stage it provides limited functions. It can be nicely connected with Post Upgrade Tests, which from my point of view is really nice. However the inability to test Side-by-Side extensions makes the usability extremely limited to core proceses.

So back to the original question on what tool to select. If your landscape is predominantly cloud based with web UIs, and you use or plan to utilize SAP Cloud ALM then simply go for the “STA or TTA integrated with SAP Cloud ALM”. If your goal is to also automate non-SAP applications and non-Web based UIs, then simply go for SAP ECT (Tricentis Tosca).

Probably it is worth to consider following aspects:

There are however some limitations for TTA/STA developers, but I will summarize them in a different blog post.

SAP Cloud ALM test automation tool for SAP S/4HANA Cloud SOLMAN Test Suite SAP Continuous Integration and Delivery

SAP Integration suite

2025-02-25T14:36:16.933000+01:00

Hi community, is there any way to connect SAP integration cloud tenant with the servers(web socket supported) through websocket communication ?

Regards,

Mohan Sai

SonarQube not picking up Code Coverage when using BTP CI/CD service

2025-03-10T13:59:29.206000+01:00

Our team recently switched to using the BTP CI/CD service instead of Jenkins in order to have a pipeline to deploy our Spring-Boot based java application to Cloud Foundry.

We are trying to perform SonarQube scans in the BTP CI/CD service, but the scan is not able to pick up Code Coverage at all, and gives 0% code coverage. We are using jacoco in order to generate code coverage, and the relevant XML file (jacoco.xml) is generated correctly in target/site/jacoco/jacoco.xml

I have tried setting the following property as well

sonar.coverage.jacoco.xmlReportPaths=target/site/jacoco/jacoco.xml

but sonarqube still can not pick up the coverage.

My stages in the CI/CD pipeline are as follows:

Could someone guide us in configuring this correctly so that the corresponding coverage is picked up?

We have a problem with some delivery plans because the cumulative total is not equal to 0.

2025-03-12T18:45:36.504000+01:00

We have a problem with some delivery plans because the cumulative total is not equal to 0.
Within the same delivery plan with the same material and the same customer, when a new EDI message is added, the system treats one delivery plan item differently than another. In one item, it sets the counter to 0 when the EDI is added, and in other items, it resets to 0.

We don't understand the criteria and need to be clear about it.

Configuring CICD For Monorepository

2025-04-30T08:20:17.176000+02:00

Hi everyone,

I'm currently working with a monorepository that contains multiple applications, including:

A frontend application
A backend service
Other supporting services

I'm using SAP CI/CD and have encountered challenges when trying to set up separate CI/CD jobs for each application within the same repository.

Challenge:

SAP CI/CD seems to only allow one .pipeline folder and one config.yml file per repository when using Infrastructure as Code (IaC). However, in a monorepo setup, I need to define different build and deployment jobs for each application (frontend, backend, etc.), ideally in isolation from each other.

What I’ve Tried:

Copying the .pipeline folder into each application directory
– This does not work. During execution, SAP CI/CD always searches for the .pipeline folder at the root of the repository. If not found there, it throws an error.
Using cd or changing directory in runFirst before a stage (e.g., cd frontend && npm install)
– This also doesn’t work. The pipeline execution seems to disregard directory changes or expects absolute control over execution flow.

What I’m Looking For:

How can I separate pipeline jobs for each application in a monorepo using SAP CI/CD?
Is there a best practice or workaround that would allow this setup with only one .pipeline/config.yml allowed?
Has anyone succeeded in setting up conditional stages, path filters, or custom scripts within a monorepo under these constraints?

Any ideas, examples, or pointers from those with experience in SAP CI/CD and monorepos would be incredibly helpful.

Thanks in advance!

SAP Continous Integration & Delivery - Branch with pattern not working

2025-05-03T15:11:30.818000+02:00

Hello experts,

We have a job in our SAP CI/CD instance which is supposed to be triggered on all the branches starting by feature. For this, we have followed the nomenclature feature*. Configuration screenshot as follows:

Unfortunately, when developers are pushing code to their respective feature branches the job is not triggered.

Based on this video tutorial, this should be possible but it is not working for us.

https://www.sap.com/assetdetail/2023/11/fa4748fb-967e-0010-bca6-c68f7e60039b.html

Any idea what we may be missing?

Thanks,

ABAP Platform pipeline in SAP CI/CD Service - release issue

2025-07-29T17:23:05.180000+02:00

Hi,

I have a problem with my ABAP Platform pipeline, using SAP Continuous Integration and Delivery Service in BTP. The issue is with the Release part.

I have a Cloud Connector and destination (using Principal Propagation) ready. The deployment from SAP BAS works as expected. All necessary OData Services are active and whitelisted. However, there's 401 error when the pipeline is executed.

[2025-07-29T14:59:03.441Z] Sending GET request to http://XXX:400/sap/opu/odata/UI5/ABAP_REPOSITORY_SRV/
[2025-07-29T14:59:03.677Z] Release stage credentials successfully validated against endpoint
...

[2025-07-29T14:59:23.345Z] info  transportRequestUploadCTS - No deploy dependencies provided. Skipping npm install call. Assuming current docker image already contains the dependencies for performing the deployment.
[2025-07-29T14:59:23.345Z] info  transportRequestUploadCTS - running shell script: /bin/sh #!/bin/sh -e
[2025-07-29T14:59:23.345Z] fiori deploy --failfast --yes --username ABAP_USER --password ABAP_PASSWORD --description "Pipeline Test" --config "ui5-deploy.yaml" --url http://XXX:400 --transport GXXXXXXXX --package Z_PACKAGE --name Z_TEST
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [32minfo[39m abap-deploy-task Z_TEST Creating archive with UI5 build result.
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [32minfo[39m abap-deploy-task Z_TEST Archive created.
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [32minfo[39m abap-deploy-task Z_TEST Starting to deploy.
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [31merror[39m abap-deploy-task Z_TEST Deployment has failed.
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [31merror[39m abap-deploy-task Z_TEST Change logging level to debug your issue
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [31merror[39m abap-deploy-task Z_TEST 	(see examples https://github.com/SAP/open-ux-tools/tree/main/packages/deploy-tooling#configuration-with-logging-enabled)
[2025-07-29T14:59:24.278Z] info  transportRequestUploadCTS - [31merror[39m builder:custom deploy-to-abap Request failed with status code 401
[2025-07-29T14:59:24.279Z] info  transportRequestUploadCTS - Command deploy failed with error : Request failed with status code 401
[2025-07-29T14:59:42.331Z] info  transportRequestUploadCTS - fatal error: errorDetails{"category":"undefined","correlationId":"n/a","error":"running shell script failed with /bin/sh: cmd.Run() failed: exit status 1","library":"SAP/jenkins-library","message":"step execution failed","result":"failure","stepName":"transportRequestUploadCTS","time":"2025-07-29T14:59:39.890292594Z"}
[2025-07-29T14:59:42.332Z] fatal transportRequestUploadCTS - step execution failed - running shell script failed with /bin/sh: cmd.Run() failed: exit status 1

I use Job Editor configuration mode. No code is used for the pipeline.

Upload credentials is Basic Auth. using my Username and Password. These are no issues with it, as I've tested successfully.

I also use Cloud Connector, with Location ID specified on the destination level.

I have a couple of doubts:

- I see the --config "ui5-deploy.yaml" is used. Is there any special ui5-deploy content I have to add? I use destination there.

- Is ABAP Platform Endpoint the URL that I can find on my Destination level?

- Location ID - documentation says it should be found on the Cloud Connector level in BTP Cockpit, but it's false. There's Location ID, but only on the Destination level.

Any idea what could be the issue?

BR,

Adrian

Technical user creation in Identity Service for implementing CI/CD ? (no email)

2025-08-19T14:28:47.809000+02:00

Hello,

The good practice for CI/CD is to use a technical user : "Use a technical user instead of your personal credentials. For more information, see Credential Handling. See Creating Credentials." (source).

I configured a custom Identity Provider (SAP Identity Services) to the cloud foundry sub-account. But, in the Identity Services, a valid email is required to configure the password... What is the proper way to create a technical user for CI/CD without an email (a password or a certificate valid for several months) ?

SAP Continuous Integration and Delivery SAP Cloud Identity Services SAP BTP, Cloud Foundry runtime and environment

Thank you

Yann

SAP BTP CI CD service for on premise S4 HANA systems RICEFW applications

2025-10-03T19:48:22.353000+02:00

Hi,

Can we use SAP BTP CI CD service for premise S4 HANA systems RICEFW applications deployment? There are only 4 pre-configured pipelines (Cloud Foundry Environment, SAP Fiori for ABAP Platform, SAP Integration Suite Artifacts, Kyma Runtime )available in CI CD service. Which pipeline to use for this on premise scenario?

Example scenario :

On premise ABAP objects development like ABAP programs written in SE38, data dictionary objects created in SE11, enhancements, smartforms, webservices etc are developed in on-premise SAP S4 HANA development system. The transport request numbers are released and are pushed to Github repository via gCTS fiori app as commits. SAP BTP CI CD pipeline job should trigger and perform the automated testing and deployment to target on premise systems(not the subaccounts but to on premise target systems like QA and production).

How to design this on-premise scenario with SAP BTP CI CD pipeline? How to automate and configure ATC checks, unit tests, integration testing, end to end testing?

Can anybody please provide inputs?

Regards,

Sunil

Test automation tools - Based on type

2025-11-04T21:10:10.072000+01:00

Hi All,

My client is asking us for Automation testing tools specific each testing type...as in best suited for different testing type.

Unit Testing

Integration Testing

Functional Testing

Regression Testing

UAT Testing

Performance Testing

Security and AUthorization Testing

We did discuss the SAP Native tools like eCatt and Solman and third party like Tosca.But, they seem to want more information and want specific automation tools addressing each type and also any Automation tool that addresses all of them. A lot of consultants i know and work with are not giving assured answers.

Any help and insights from people who have information is welcome.

Thanks All.

RAP events feasibility after advance event mesh available for client

2025-12-09T14:36:48.208000+01:00

We have implemented Restful application programming (RAP) for delivery business objects and it is working as expected. Now AEM (Advance event mesh) will be available in client landscape. So we need to know what kind of retrofitting we need to do when the RAP solution is working with AEM. Please suggest some sap links which can be useful to understand the basic of advance event mesh.

gCTS Disadvantages - Experiences

2026-02-03T12:01:17.638000+01:00

Hello Community,
we are considering introducing the Git‑based version control that is natively supported by S/4HANA.
Does anyone have real‑life experience with it?
I am also very interested in any disadvantages or obstacles you may have encountered.

Thanks in advance for any answers.

Ralf