- SAP Community
- Groups
- Interest Groups
- SAP Learning Groups
- SAP Learning
- Q&A
- CLD200 Verifying the Build Success failed
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
CLD200 Verifying the Build Success failed
simonpolovina1
Participant
Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 2023 Feb 18 5:36 PM - last edited on 2023 Feb 21 12:20 AM by Former Member
1,429
Hi. My Build in the CLD200 Verifying the Build Success exercise failed. Please advise. Here's the full log, as requested:
Build Logs (risk-management-job #2)
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.267.0
Attempting to resolve v1.267.0 from remote references...
> git --version # timeout=10
> git --version # 'git version 2.36.4'
> git ls-remote -- https://github.com/SAP/jenkins-library.git # timeout=10
Found match: refs/tags/v1.267.0 revision 4a1cf4fd45dd75fe79f19e6d37ca03fa5883a4a7
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.36.4'
> 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.267.0^{commit} # timeout=10
Resolved tag v1.267.0 revision 4a1cf4fd45dd75fe79f19e6d37ca03fa5883a4a7
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/risk-management-job@libs/7087cd5607ba78f19e3ffbc3d05f0ae2172da46cbb349a206eb84cf95dbb2246 # timeout=10
Fetching upstream changes from https://github.com/SAP/jenkins-library.git
> git --version # timeout=10
> git --version # 'git version 2.36.4'
> 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 4a1cf4fd45dd75fe79f19e6d37ca03fa5883a4a7 (v1.267.0)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4a1cf4fd45dd75fe79f19e6d37ca03fa5883a4a7 # timeout=10
Commit message: "feat(codeql): added stashes (#4196)"
First time build. Skipping changelog.
[Pipeline] library
Loading library cloudci-lib@v3.3.2
Attempting to resolve v3.3.2 from remote references...
> git --version # timeout=10
> git --version # 'git version 2.36.4'
> git ls-remote -- http://cloudci-git-mirror.cloudci-git-mirror.svc.cluster.local/git/cloudci/pipeline-lib.git # timeout=10
Found match: refs/tags/v3.3.2 revision 4523af1fa1129225d0090d109bc6859d3e56b902
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.36.4'
> 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/v3.3.2^{commit} # timeout=10
Resolved tag v3.3.2 revision 4523af1fa1129225d0090d109bc6859d3e56b902
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/risk-management-job@libs/8cfca526664da51d4757004f4dc1ede15cd934d619d40a2da6b7e91b78b164b6 # 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.36.4'
> 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 4523af1fa1129225d0090d109bc6859d3e56b902 (v3.3.2)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4523af1fa1129225d0090d109bc6859d3e56b902 # timeout=10
Commit message: "[DO_NOT_MERGE] Update node browser SHAs (#147)"
First time build. Skipping changelog.
[Pipeline] node
Running on Jenkins in /jenkins_home/workspace/risk-management-job
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Init)
[Pipeline] script
[Pipeline] {
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] checkout
[2023-02-18T17:17:06.987Z] The recommended git tool is: NONE
[2023-02-18T17:17:07.073Z] No credentials specified
[2023-02-18T17:17:07.109Z] Cloning the remote Git repository
[2023-02-18T17:17:07.142Z] Cloning repository https://github.com/simonpolovina/RiskManagement.git
[2023-02-18T17:17:07.178Z] > git init /jenkins_home/workspace/risk-management-job # timeout=10
[2023-02-18T17:17:07.219Z] Fetching upstream changes from https://github.com/simonpolovina/RiskManagement.git
[2023-02-18T17:17:07.253Z] > git --version # timeout=10
[2023-02-18T17:17:07.292Z] > git --version # 'git version 2.36.4'
[2023-02-18T17:17:07.329Z] > git fetch --tags --force --progress -- https://github.com/simonpolovina/RiskManagement.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2023-02-18T17:17:08.167Z] > git config remote.origin.url https://github.com/simonpolovina/RiskManagement.git # timeout=10
[2023-02-18T17:17:08.227Z] > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2023-02-18T17:17:08.270Z] Avoid second fetch
[2023-02-18T17:17:08.312Z] > git rev-parse origin/main^{commit} # timeout=10
[2023-02-18T17:17:08.352Z] Checking out Revision be1c60d60f032d6001d4da98e57b7ed62b850173 (origin/main)
[2023-02-18T17:17:08.386Z] > git config core.sparsecheckout # timeout=10
[2023-02-18T17:17:08.456Z] > git checkout -f be1c60d60f032d6001d4da98e57b7ed62b850173 # timeout=10
[2023-02-18T17:17:08.506Z] Commit message: "Update TROUBLESHOOTING.md"
[2023-02-18T17:17:08.541Z] First time build. Skipping changelog.
[Pipeline] writeFile
[Pipeline] readYaml
[Pipeline] echo
[2023-02-18T17:17:08.958Z] Using configuration setup from the UI.
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] writeYaml
[Pipeline] writeFile
[Pipeline] stash
[2023-02-18T17:17:09.931Z] Stashed 52 file(s)
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] lock
[2023-02-18T17:17:15.484Z] Trying to acquire lock on [risk-management-job/1]
[2023-02-18T17:17:15.575Z] Resource [risk-management-job/1] did not exist. Created.
[2023-02-18T17:17:15.610Z] Lock acquired on [risk-management-job/1]
[Pipeline] {
[Pipeline] milestone
[2023-02-18T17:17:15.844Z] Trying to pass milestone 1
[Pipeline] node
[2023-02-18T17:17:16.633Z] Running on Jenkins in /jenkins_home/workspace/risk-management-job@2
[Pipeline] {
[Pipeline] deleteDir
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] echo
[2023-02-18T17:17:17.289Z] Unstash content: checkoutstash
[Pipeline] unstash
[Pipeline] echo
[2023-02-18T17:17:18.714Z] --- Begin library step of: setupCommonPipelineEnvironment ---
[Pipeline] fileExists
[Pipeline] readYaml
[Pipeline] libraryResource
[Pipeline] writeFile
[Pipeline] fileExists
[Pipeline] readFile
[Pipeline] writeFile
[Pipeline] libraryResource
[Pipeline] readYaml
[Pipeline] echo
[2023-02-18T17:17:20.570Z] Loading configuration file '.pipeline/cicdCustomDefaults.yml'
[Pipeline] readYaml
[Pipeline] echo
[2023-02-18T17:17:21.387Z] --- Begin library step of: piperLoadGlobalExtensions ---
[Pipeline] echo
[2023-02-18T17:17:21.768Z] --- End library step of: piperLoadGlobalExtensions ---
[Pipeline] stash
[2023-02-18T17:17:22.007Z] Stashed 4 file(s)
[Pipeline] echo
[2023-02-18T17:17:22.376Z] [setupCommonPipelineEnvironment] Sending telemetry data is disabled.
[Pipeline] echo
[2023-02-18T17:17:22.652Z] --- End library step of: setupCommonPipelineEnvironment ---
[Pipeline] findFiles
[Pipeline] error
[Pipeline] deleteDir
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[2023-02-18T17:17:24.069Z] Lock released on resource [risk-management-job/1]
[Pipeline] // lock
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
Stage "Build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Additional Unit Tests)
Stage "Additional Unit Tests" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Acceptance)
Stage "Acceptance" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Compliance)
Stage "Compliance" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Release)
Stage "Release" skipped due to earlier failure(s)
[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: [piperPipelineStageInit] buildTool configuration 'mta' does not fit to your project (buildDescriptorPattern: 'mta.yaml'), please set buildTool as general setting in your .pipeline/config.yml correctly, see also https://sap.github.io/jenkins-library/configuration/
Finished: FAILURE
markushaug
Product and Topic Expert
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
2023 Feb 23
1:20 PM
Hi Simon,
can you add a ".npmrc" file in your project root directory? And add the following line there:
"registry=https://registry.npmjs.com/"
Like in the starter template: https://github.com/SAP-samples/btp-side-by-side-extension-learning-journey/blob/main/.npmrc
"npm ERR! network request to http://nginx-redirector.repo-cache.svc.cluster.local/repository/appstudio-npm-group/@sap/audit-loggi... failed, reason: getaddrinfo ENOTFOUND nginx-redirector.repo-cache.svc.cluster.local"
As you can see, npm is not finding the package. If the explicit definition of the registry won't help, I also suggest removing the node_modules folder and the package-lock.json file and run "npm i" again to get a fresh package-lock-json in your project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
simonpolovina1
Participant
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
2023 Feb 23
1:30 PM
Hi Markus. In the event, I reworked the exercises in the Automated Deployment unit, and it worked. Nonetheless, your above answers gave me insight into the structure and potential issues. Most valuable - thanks! Simon
markushaug
Product and Topic Expert
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
2023 Feb 24
10:29 AM
Ask a Question
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.