error build

Skip to content
[Jenkins]Jenkins
Search (⌘+K)
developer

log out
Dashboard
kms-frontend-develop
#257
Pipeline Console
 Build #257
Overview

Failed 1 hr 35 min ago in 7 min 27 sec

SET-ENV
SCM
SonarQube Analysis
CLOUD AUTH
IMAGE PUSH
DELETE UNUSED IMAGE
Helm-Update
Post Actions
Stage 'IMAGE PUSH'

Started 1 hr 32 min ago
Queued 0 ms
Took 3 min 45 sec
failure
View as plain text
docker build -f Dockerfile.staging -t asia-southeast2-docker.pkg.dev/pelindo-back-office/portaverse/kms-frontend:stg-257 .
Shell Script
3 min 41 sec
Jenkins 2.452.1
docker build -f Dockerfile.staging -t asia-southeast2-docker.pkg.dev/pelindo-back-office/portaverse/kms-frontend:stg-257 . - Shell Script
Close
found in the cache and will be fetched from the remote registry
#14 66.17 ➤ YN0013: │ punycode.js@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.17 ➤ YN0013: │ punycode@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ protobufjs@npm:6.11.4 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ protobufjs@npm:7.4.0 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ punycode.js@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ punycode@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ qs@npm:6.13.0 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ protobufjs@npm:7.4.0 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ punycode.js@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ punycode@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ qs@npm:6.13.0 can't be found in the cache and will be fetched from the remote registry
#14 66.18 ➤ YN0013: │ query-string@npm:8.2.0 can't be found in the cache and will be fetched from the remote registry
#14 66.20 ➤ YN0013: │ punycode.js@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.20 ➤ YN0013: │ punycode@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.20 ➤ YN0013: │ qs@npm:6.13.0 can't be found in the cache and will be fetched from the remote registry
#14 66.20 ➤ YN0013: │ query-string@npm:8.2.0 can't be found in the cache and will be fetched from the remote registry
#14 66.20 ➤ YN0013: │ queue-microtask@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ punycode@npm:2.3.1 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ qs@npm:6.13.0 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ query-string@npm:8.2.0 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ queue-microtask@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ quick-lru@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ qs@npm:6.13.0 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ query-string@npm:8.2.0 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ queue-microtask@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ quick-lru@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.21 ➤ YN0013: │ raf-schd@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ query-string@npm:8.2.0 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ queue-microtask@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ quick-lru@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ raf-schd@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ raf@npm:3.4.1 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ queue-microtask@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ quick-lru@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ raf-schd@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ raf@npm:3.4.1 can't be found in the cache and will be fetched from the remote registry
#14 66.26 ➤ YN0013: │ rangetouch@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.27 ➤ YN0013: │ quick-lru@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
#14 66.27 ➤ YN0013: │ raf-schd@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
#14 66.27 ➤ YN0013: │ raf@npm:3.4.1 can't be found in the cache and will be fetched from the remote registry
#14 66.27 ➤ YN0013: │ rangetouch@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
#15 DONE 9.6s
#16 [builder 9/9] RUN yarn build
#16 19.30 YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 37, column 10:
#16 19.30       version: 7.25.2
#16 19.30              ^
#16 19.30       version: 7.25.2
#16 19.30              ^
#16 19.30     at kU (/app/.yarn/releases/yarn-3.2.0.cjs:13:789)
#16 19.30     at dt (/app/.yarn/releases/yarn-3.2.0.cjs:13:891)
#16 19.30     at Vpe (/app/.yarn/releases/yarn-3.2.0.cjs:20:1609)
#16 19.30     at rg (/app/.yarn/releases/yarn-3.2.0.cjs:20:4422)
#16 19.30     at ede (/app/.yarn/releases/yarn-3.2.0.cjs:20:6569)
#16 19.30     at RU (/app/.yarn/releases/yarn-3.2.0.cjs:21:260)
#16 19.30     at NU (/app/.yarn/releases/yarn-3.2.0.cjs:21:481)
#16 19.30     at rde (/app/.yarn/releases/yarn-3.2.0.cjs:21:759)
#16 19.30     at Gde (/app/.yarn/releases/yarn-3.2.0.cjs:331:142)
#16 19.30     at Qi (/app/.yarn/releases/yarn-3.2.0.cjs:331:490)
#16 ERROR: process "/bin/sh -c yarn build" did not complete successfully: exit code: 1
------
 > [builder 9/9] RUN yarn build:
19.30     at kU (/app/.yarn/releases/yarn-3.2.0.cjs:13:789)
19.30     at dt (/app/.yarn/releases/yarn-3.2.0.cjs:13:891)
19.30     at Vpe (/app/.yarn/releases/yarn-3.2.0.cjs:20:1609)
19.30     at rg (/app/.yarn/releases/yarn-3.2.0.cjs:20:4422)
19.30     at ede (/app/.yarn/releases/yarn-3.2.0.cjs:20:6569)
19.30     at RU (/app/.yarn/releases/yarn-3.2.0.cjs:21:260)
19.30     at NU (/app/.yarn/releases/yarn-3.2.0.cjs:21:481)
19.30     at rde (/app/.yarn/releases/yarn-3.2.0.cjs:21:759)
19.30     at Gde (/app/.yarn/releases/yarn-3.2.0.cjs:331:142)
19.30     at Qi (/app/.yarn/releases/yarn-3.2.0.cjs:331:490)
------
Dockerfile.staging:78
--------------------
  76 |     
  77 |     
  78 | >>> RUN yarn build
  79 |     
  80 |     ##CMD ["yarn", "start"]
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn build" did not complete successfully: exit code: 1
script returned exit code 1